Get detailed information about available search modes and current capabilities
AI agents call get_search_capabilities to retrieve information from RAGex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns information about available search modes and current system capabilities. It is a read-only query operation that does not modify, execute, delete, or move any data. The low severity reflects minimal blast radius if misused—an AI agent obtaining search capability information poses no direct risk to data integrity or operations.
From the tool's definition Tool name 'get_search_capabilities' and description 'Get detailed information about available search modes and current capabilities' indicate retrieval of metadata/capability information with no side effects.
Documented attack patterns abuse exactly the kind of access get_search_capabilities gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and RAGex, and nothing reaches the server without passing your rules. This is the rule we recommend for get_search_capabilities:
{
"version": "1",
"default": "deny",
"tools": {
"get_search_capabilities": {}
}
}get_search_capabilities 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.
Get detailed information about available search modes and current capabilities. It is categorised as a Read tool in the RAGex MCP Server, which means it retrieves data without modifying state.
Register the RAGex MCP server in PolicyLayer and add a rule for get_search_capabilities: 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 RAGex. Nothing to install.
get_search_capabilities 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 get_search_capabilities 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 get_search_capabilities. 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.
get_search_capabilities is provided by the RAGex MCP server (jbenshetler/mcp-ragex). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from RAGex, 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.
4 RAGex tools catalogued and risk-classified — across an index of 43,000+ MCP servers.