Check MongoDB connectivity separately from server health.
AI agents call database_status to retrieve information from DataFlow MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a health check/status query operation on MongoDB connectivity. It has no side effects, makes no modifications to data, and simply retrieves diagnostic information. This is a classic Read operation with minimal blast radius - an AI agent misusing this tool cannot cause harm beyond potentially detecting database unavailability, which has low impact. Low severity is appropriate for diagnostic queries.
From the tool's definition Tool name is 'database_status' and description states 'Check MongoDB connectivity separately from server health' - this is a diagnostic query operation that retrieves status information without modifying any data.
Attacks that exploit this kind of access
Check MongoDB connectivity separately from server health. It is categorised as a Read tool in the DataFlow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DataFlow MCP Server MCP server in PolicyLayer and add a rule for database_status: 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 DataFlow MCP Server. Nothing to install.
database_status 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_status 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_status. 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_status is provided by the DataFlow MCP Server MCP server (sreetarak2/dataflow_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 →