AI agents call corn_health to retrieve information from CornMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves system status and metadata information without modifying, executing, or destroying any data. It is a passive monitoring/diagnostic function that queries system state. The low severity reflects that misuse of this tool would not significantly impact data integrity, security, or operations — an agent querying health status repeatedly poses minimal risk.
From the tool's definition Tool description explicitly states 'Check Corn Hub system health — services, uptime, version'. The verb 'check' and the read-only nature of querying health status, uptime, and version information indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access corn_health gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CornMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for corn_health:
{
"version": "1",
"default": "deny",
"tools": {
"corn_health": {}
}
}corn_health is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check Corn Hub system health — services, uptime, version. It is categorised as a Read tool in the CornMCP MCP Server, which means it retrieves data without modifying state.
Register the Corn MCP server in PolicyLayer and add a rule for corn_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 CornMCP. Nothing to install.
corn_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 corn_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 corn_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.
corn_health is provided by the Corn MCP server (yuki-20/cornmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 18 CornMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
18 CornMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.