database_stats
Return SQLite context store table counts and database path.
This record as markdown: /tools/mcp-control-plane/database-stats.md
What database_stats does on Mcp Control Plane
AI agents call database_stats to retrieve information from Mcp Control Plane without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why database_stats is rated Low
This tool retrieves statistics about an SQLite database (table counts and path information). It performs a read-only query that returns metadata about the database structure without creating, modifying, deleting, or executing any code. The action is non-destructive and has minimal security impact, even if misused by an agent.
From the tool's definition Tool name is 'database_stats' and description states it 'Return[s] SQLite context store table counts and database path' — purely informational retrieval with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs database_stats safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For database_stats, this is the rule to start with:
database_stats is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every database_stats call is checked against it from then on.
Questions about database_stats
Return SQLite context store table counts and database path. It is categorised as a Read tool in the Mcp Control Plane MCP Server, which means it retrieves data without modifying state.
Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for database_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 Control Plane. Nothing to install.
database_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 database_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 database_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.
database_stats is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Control Plane, and thousands of servers like it.
This server
Across the catalogue