Task-to-events matcher. Use when you need event names for handlers/triggers (e.g., resource lifecycle, player joins, marker hits). Returns ranked MTA:SA events only.
AI agents call find_events_for_task to retrieve information from MTA:SA Documentation MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs intelligent search and matching against MTA:SA event documentation. It retrieves event information based on task descriptions but does not create, modify, delete, or execute anything. It is purely informational/query-based, consistent with sibling tools like search_events and search_functions which are clearly read-only operations.
From the tool's definition Tool description states it 'Use when you need event names for handlers/triggers' and 'Returns ranked MTA:SA events only.' This is a search/lookup function that retrieves documentation information about events without modifying any data or executing code.
Attacks that exploit this kind of access
Task-to-events matcher. Use when you need event names for handlers/triggers (e.g., resource lifecycle, player joins, marker hits). Returns ranked MTA:SA events only. It is categorised as a Read tool in the MTA:SA Documentation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MTA:SA Documentation MCP Server MCP server in PolicyLayer and add a rule for find_events_for_task: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches MTA:SA Documentation MCP Server. Nothing to install.
find_events_for_task is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the find_events_for_task rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for find_events_for_task. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
find_events_for_task is provided by the MTA:SA Documentation MCP Server MCP server (mtasa-docs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →