Search for available RPG tools by category, capability, or keyword. Use this to discover tools before using them.
AI agents call search_tools to retrieve information from Rpg without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about available tools on the RPG-MCP server. It performs no actions, creates no entities, executes no commands, and modifies no game state. The capability to discover tools is a read-only informational function analogous to listing or searching a directory.
From the tool's definition Tool name is 'search_tools' and description states it 'Search[es] for available RPG tools by category, capability, or keyword' with purpose to 'discover tools before using them.' This is a pure query/discovery operation with no side effects, data…
Documented attack patterns abuse exactly the kind of access search_tools gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Rpg, and nothing reaches the server without passing your rules. This is the rule we recommend for search_tools:
{
"version": "1",
"default": "deny",
"tools": {
"search_tools": {}
}
} search_tools is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search for available RPG tools by category, capability, or keyword. Use this to discover tools before using them. It is categorised as a Read tool in the Rpg MCP Server, which means it retrieves data without modifying state.
Register the Rpg MCP server in PolicyLayer and add a rule for search_tools: 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 Rpg. Nothing to install.
search_tools 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_tools 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_tools. 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_tools is provided by the Rpg MCP server (mnehmos/mnehmos.rpg.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Rpg, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
47 Rpg tools catalogued and risk-classified — across an index of 43,000+ MCP servers.