End the current work session. Provide a summary of changes and decisions for handoff.
AI agents use corn_session_end to create or update resources in CornMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CornMCP environment.
This tool ends a session and stores/records a summary for handoff purposes. It writes/commits session state and summary data, but does not delete data or execute code. The primary action is finalizing and recording session information, which is a Write operation. Severity is low as misuse would at most result in an incorrect session summary.
From the tool's definition End the current work session. Provide a summary of changes and decisions for handoff.
Documented attack patterns abuse exactly the kind of access corn_session_end 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_session_end:
{
"version": "1",
"default": "deny",
"tools": {
"corn_session_end": {
"limits": [
{
"counter": "corn_session_end_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}corn_session_end stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
End the current work session. Provide a summary of changes and decisions for handoff. It is categorised as a Write tool in the CornMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Corn MCP server in PolicyLayer and add a rule for corn_session_end: 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_session_end is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the corn_session_end 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_session_end. 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_session_end 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.