getDatabaseStats
AI agents call getDatabaseStats to retrieve information from AWS IoT SiteWise MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Database statistics queries are typically read-only operations that retrieve metrics about database performance, size, or status without altering data or system state. The absence of modification keywords (create, update, delete, set) and the purely informational nature of statistics retrieval places this in the Read category with low severity. Confidence is reduced due to empty description.
From the tool's definition Tool name 'getDatabaseStats' indicates retrieval of database statistics without modification. Description is empty, limiting certainty, but the 'get' prefix and 'Stats' suffix are characteristic of read-only operations.
Attacks that exploit this kind of access
getDatabaseStats. It is categorised as a Read tool in the AWS IoT SiteWise MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for getDatabaseStats: 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 AWS IoT SiteWise MCP Server. Nothing to install.
getDatabaseStats 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 getDatabaseStats 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 getDatabaseStats. 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.
getDatabaseStats is provided by the AWS IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.