Get database statistics
AI agents call get_database_stats to retrieve information from Google Tag Manager MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves database statistics without modifying, deleting, or executing operations. It is a pure information retrieval action, fitting the Read category with low severity due to minimal blast radius—misuse would only expose metrics or performance data rather than cause damage or unauthorized modifications.
From the tool's definition Tool name 'get_database_stats' and description 'Get database statistics' indicate a retrieval operation with no side effects. The verb 'get' and 'statistics' clearly denote read-only querying.
Attacks that exploit this kind of access
Get database statistics. It is categorised as a Read tool in the Google Tag Manager MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Tag Manager MCP Server MCP server in PolicyLayer and add a rule for get_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 Google Tag Manager MCP Server. Nothing to install.
get_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 get_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 get_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.
get_database_stats is provided by the Google Tag Manager MCP Server MCP server (neep305/mcp-for-gtm). 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 →