Health snapshot of the wafle backend: db / redis / upstream catalog / WooCommerce core. Returns latency per check.\n\n
AI agents call wafle_system_health to retrieve information from wafle MCP server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the current state of backend systems (database, Redis, upstream catalog, WooCommerce core) and returns diagnostic metrics. It performs no modifications, deletions, or operations that trigger external side effects. It is a monitoring/observability tool that reads and reports system status, fitting the Read category with low severity since misuse poses minimal risk to data or systems.
From the tool's definition Tool name 'wafle_system_health' and description 'Health snapshot' indicating it retrieves status information. Returns 'latency per check' — purely observational data with no side effects.
Attacks that exploit this kind of access
Health snapshot of the wafle backend: db / redis / upstream catalog / WooCommerce core. Returns latency per check.\n\n. It is categorised as a Read tool in the wafle MCP server MCP Server, which means it retrieves data without modifying state.
Register the wafle MCP server MCP server in PolicyLayer and add a rule for wafle_system_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 wafle MCP server. Nothing to install.
wafle_system_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 wafle_system_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 wafle_system_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.
wafle_system_health is provided by the wafle MCP server MCP server (the33warehouse-tech/wafle-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 →