Comprehensive MongoDB health check: server status, replication, connections, memory, operations.
AI agents call mongo_health_check to retrieve information from RedisNexus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves diagnostic information about MongoDB server state (status, replication state, connection counts, memory usage, operation metrics) without making any changes to data or triggering operational actions. It is purely observational/informational, fitting the Read category. The low severity reflects minimal blast radius—health check data disclosure poses no immediate operational risk.
From the tool's definition Tool description explicitly states 'health check' with read-only operations: 'server status, replication, connections, memory, operations'. These are all query/monitoring operations with no data modification or side effects.
Attacks that exploit this kind of access
Comprehensive MongoDB health check: server status, replication, connections, memory, operations. It is categorised as a Read tool in the RedisNexus MCP Server, which means it retrieves data without modifying state.
Register the RedisNexus MCP server in PolicyLayer and add a rule for mongo_health_check: 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 RedisNexus. Nothing to install.
mongo_health_check 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 mongo_health_check 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 mongo_health_check. 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.
mongo_health_check is provided by the RedisNexus MCP server (rajkumar-madhu/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 →