db_get_stats
AI agents call db_get_stats to retrieve information from Skyfly MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'db_get_stats' and its position among other query/retrieval tools on a data-enrichment server indicates it retrieves statistics without modification. The description is empty, which reduces confidence slightly, but the consistent pattern of sibling 'db_get_*' and 'db_lookup_*' tools all being read operations strongly suggests this is also a read-only query tool with no side effects or data modification…
From the tool's definition Tool name 'db_get_stats' and context of sibling tools (db_get_engine_info, db_get_model_info, db_get_reference_codes, db_lookup_*) all perform data retrieval operations.
Attacks that exploit this kind of access
db_get_stats. It is categorised as a Read tool in the Skyfly MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Skyfly MCP Server MCP server in PolicyLayer and add a rule for db_get_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 Skyfly MCP Server. Nothing to install.
db_get_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 db_get_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 db_get_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.
db_get_stats is provided by the Skyfly MCP Server MCP server (vog01r/skyfly-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 →