Check if Nexus Memory is running and healthy.
AI agents call health to retrieve information from Nexus Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries the operational status of the Nexus Memory service. It retrieves health information without modifying, executing, or deleting any data. Misuse potential is minimal as it only exposes service availability status.
From the tool's definition 'Check if Nexus Memory is running and healthy' — a status/health check with no side effects
Attacks that exploit this kind of access
Check if Nexus Memory is running and healthy. It is categorised as a Read tool in the Nexus Memory MCP Server, which means it retrieves data without modifying state.
Register the Nexus Memory MCP server in PolicyLayer and add a rule for health: 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 Nexus Memory. Nothing to install.
health 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 health 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 health. 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.
health is provided by the Nexus Memory MCP server (neboy72/nexus-memory). 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 →