Get statistics about the smart suggestions knowledge base, including total patterns and categorization.
AI agents call get_knowledge_base_stats to retrieve information from MCP DevTools Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves aggregate statistics about a knowledge base. It performs a read-only query operation without modifying, executing external operations, deleting data, or moving money. The blast radius of misuse is minimal—an AI could at most retrieve harmless summary statistics. Low severity is appropriate for informational queries.
From the tool's definition Tool name 'get_knowledge_base_stats' and description 'Get statistics about the smart suggestions knowledge base' indicate a query/retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_knowledge_base_stats gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP DevTools Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_knowledge_base_stats:
{
"version": "1",
"default": "deny",
"tools": {
"get_knowledge_base_stats": {}
}
} get_knowledge_base_stats 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 statistics about the smart suggestions knowledge base, including total patterns and categorization. It is categorised as a Read tool in the MCP DevTools Server MCP Server, which means it retrieves data without modifying state.
Register the MCP DevTools Server MCP server in PolicyLayer and add a rule for get_knowledge_base_stats: 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 MCP DevTools Server. Nothing to install.
get_knowledge_base_stats 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_knowledge_base_stats 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_knowledge_base_stats. 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_knowledge_base_stats is provided by the MCP DevTools Server MCP server (rshade/mcp-devtools-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP DevTools Server, 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.
79 MCP DevTools Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.