Event discovery tool. Search MTA:SA client/server events only (not regular functions), then chain into docs tools with exact event names.
AI agents call search_events 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 retrieves and discovers event information from documentation without creating, modifying, deleting, or executing any code. It is a search/query operation returning reference data, which is the definition of a Read category tool. Severity is low because searching documentation poses minimal risk even if misused by an AI agent.
From the tool's definition Tool is described as an 'Event discovery tool' that performs 'Search' operations on MTA:SA events. The verb 'search' and the focus on discovery and retrieval with chaining to 'docs tools' indicate read-only querying without data modification or execution.
Attacks that exploit this kind of access
Event discovery tool. Search MTA:SA client/server events only (not regular functions), then chain into docs tools with exact event names. 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 search_events: 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.
search_events 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 search_events 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 search_events. 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.
search_events 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 →