Primary discovery tool. Search MTA:SA functions and events by name or keyword before coding. Returns canonical function names with side/category so LLMs can reliably chain into docs tools.
AI agents call search_functions 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.
The search_functions tool retrieves documentation and function metadata without executing code, modifying data, or triggering external operations. It is a discovery mechanism that returns information about available functions. All sibling tools confirm this is a read-only documentation server (get_function_docs, get_function_examples, list_functions_by_category, etc.).
From the tool's definition Tool description states it "Search[es] MTA:SA functions and events by name or keyword" and "Returns canonical function names" — these are purely informational retrieval operations with no modification or execution of code.
Attacks that exploit this kind of access
Primary discovery tool. Search MTA:SA functions and events by name or keyword before coding. Returns canonical function names with side/category so LLMs can reliably chain into docs tools. 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_functions: 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_functions 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_functions 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_functions. 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_functions 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 →