Check connection to WordPress and plugin status
AI agents call health_check to retrieve information from Noleemits Vision Builder MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only health check—it queries the current state of a WordPress connection and plugin status but does not create, modify, delete, or execute any operations. It has minimal blast radius if misused by an AI agent, as it only retrieves information.
From the tool's definition The tool name 'health_check' and description 'Check connection to WordPress and plugin status' indicate a diagnostic query operation that retrieves status information without modifying, executing external operations, or having destructive effects.
Attacks that exploit this kind of access
Check connection to WordPress and plugin status. It is categorised as a Read tool in the Noleemits Vision Builder MCP MCP Server, which means it retrieves data without modifying state.
Register the Noleemits Vision Builder MCP server in PolicyLayer and add a rule for 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 Noleemits Vision Builder MCP. Nothing to install.
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 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 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.
health_check is provided by the Noleemits Vision Builder MCP server (noleemits/vision-builder-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 →