Skip to main content
Glama
malloryai

Mallory MCP Server

Official
by malloryai

get_mentioned_threat_actors

Monitor recent threat actor activities mentioned in threat intelligence sources to track emerging threats, identify active actors, and build situational awareness of the current threat landscape.

Instructions

Get mentioned threat actors

Use this tool when you need to monitor recent threat actor activities mentioned in threat intelligence sources. This is especially valuable for:

  • Tracking emerging threats and active threat actors

  • Monitoring the latest threat intelligence reporting

  • Identifying which threat actors are currently active or trending

  • Building situational awareness of the current threat landscape

  • Obtaining recent summaries of threat actor tactics and campaigns

Unlike list_threat_actors() which returns basic threat actor records, this function returns actual mentions with context from recent intelligence sources.

Args: offset (int, optional): The number of items to skip before starting to collect the result set. Defaults to 0. limit (int, optional): The maximum number of items to return. Minimum value is 1. Defaults to 10. sort (str, optional): Field to sort by - either 'name', 'created_at', or 'updated_at'. Defaults to 'created_at'. order (str, optional): Sort order - either 'asc' or 'desc'. Defaults to 'desc'.

Returns: Dict[str, Any]: Dictionary containing: - total: Total number of threat actor mentions available - offset: Current pagination offset - limit: Number of items returned per page - message: Status message (usually null when successful) - data: List of recent threat actor mentions, each containing: - uuid: Unique identifier for this mention - overview: Summary of the threat actor's recent activities or campaigns - created_at: Timestamp when this mention was first added to the system - updated_at: Timestamp when this mention was last updated - published_at: Original publication date of the source material - collected_at: When this intelligence was collected - reference_url: URL of the source article or report - reference_source: Name of the intelligence source (e.g., "securityaffairs") - reference_user_generated_content: Whether this is from user-generated content - threat_actor_uuid: UUID of the referenced threat actor - threat_actor_name: Name of the referenced threat actor

This function provides timely intelligence about threat actors from recently published sources, making it ideal for staying current on the threat landscape.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offsetNo
limitNo
sortNocreated_at
orderNodesc

Implementation Reference

  • The handler function decorated with @mcp.tool() for the get_mentioned_threat_actors tool. It accepts pagination and sorting parameters and delegates to the malloryai_client to fetch mentioned threat actors, including detailed docstring for schema.
    @mcp.tool()
    @handle_api_errors
    async def get_mentioned_threat_actors(
        offset: int = 0,
        limit: int = 10,
        sort: str = "created_at",
        order: str = "desc",
    ) -> Dict[str, Any]:
        """Get mentioned threat actors
    
        Use this tool when you need to monitor recent threat actor activities mentioned in
        threat intelligence sources. This is especially valuable for:
        - Tracking emerging threats and active threat actors
        - Monitoring the latest threat intelligence reporting
        - Identifying which threat actors are currently active or trending
        - Building situational awareness of the current threat landscape
        - Obtaining recent summaries of threat actor tactics and campaigns
    
        Unlike list_threat_actors() which returns basic threat actor records, this function
        returns actual mentions with context from recent intelligence sources.
    
        Args:
            offset (int, optional): The number of items to skip before starting to collect the result set. Defaults to 0.
            limit (int, optional): The maximum number of items to return. Minimum value is 1. Defaults to 10.
            sort (str, optional): Field to sort by - either 'name', 'created_at', or 'updated_at'. Defaults to 'created_at'.
            order (str, optional): Sort order - either 'asc' or 'desc'. Defaults to 'desc'.
    
        Returns:
            Dict[str, Any]: Dictionary containing:
                - total: Total number of threat actor mentions available
                - offset: Current pagination offset
                - limit: Number of items returned per page
                - message: Status message (usually null when successful)
                - data: List of recent threat actor mentions, each containing:
                    - uuid: Unique identifier for this mention
                    - overview: Summary of the threat actor's recent activities or campaigns
                    - created_at: Timestamp when this mention was first added to the system
                    - updated_at: Timestamp when this mention was last updated
                    - published_at: Original publication date of the source material
                    - collected_at: When this intelligence was collected
                    - reference_url: URL of the source article or report
                    - reference_source: Name of the intelligence source (e.g., "securityaffairs")
                    - reference_user_generated_content: Whether this is from user-generated content
                    - threat_actor_uuid: UUID of the referenced threat actor
                    - threat_actor_name: Name of the referenced threat actor
    
        This function provides timely intelligence about threat actors from recently published
        sources, making it ideal for staying current on the threat landscape.
        """
        return await malloryai_client.threat_actors.list_threat_actors_mentioned(
            offset=offset, limit=limit, sort=sort, order=order
        )
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the tool's behavior: it's a read operation (implied by 'Get' and 'monitor'), returns paginated results with offset/limit parameters, includes sorting options, and provides detailed return data structure. It also mentions the tool's value for 'timely intelligence' and 'staying current,' though it doesn't specify rate limits or authentication requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections: purpose statement, usage guidelines, parameter documentation, and return value explanation. While comprehensive (necessary given the lack of annotations and output schema), it's efficiently organized with bullet points for scenarios and a detailed Returns section. Some sentences could be more concise, but overall it's appropriately sized for the complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (4 parameters, no annotations, no output schema), the description provides complete context. It covers purpose, usage guidelines, parameter semantics, and a detailed return structure. The Returns section documents all fields in the response dictionary, compensating for the missing output schema. This makes the tool fully understandable to an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage (no descriptions in the input schema), the description fully compensates by providing detailed parameter documentation. It explains all four parameters (offset, limit, sort, order) with their purposes, default values, constraints (e.g., 'Minimum value is 1'), and allowed values (e.g., sort fields and order options). This adds significant meaning beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose as 'Get mentioned threat actors' and elaborates that it returns 'actual mentions with context from recent intelligence sources.' It explicitly distinguishes this from the sibling tool 'list_threat_actors()' which returns 'basic threat actor records,' providing specific differentiation. The description uses precise verbs like 'monitor,' 'track,' and 'obtain' to clarify the action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage guidelines with 'Use this tool when you need to monitor recent threat actor activities mentioned in threat intelligence sources.' It lists five specific scenarios (e.g., 'Tracking emerging threats') and clearly contrasts it with 'list_threat_actors()' as an alternative for basic records. This gives comprehensive guidance on when to use this tool versus others.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/malloryai/mallory-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server