Medium Risk

close_session

Close an active session. Session file preserved for future load_session.

Part of the Mcacp server.

close_session can modify Mcacp data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE MCACP →

Free to start. No card required.

AI agents use close_session to create or modify resources in Mcacp. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call close_session repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Mcacp.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "close_session": {
      "limits": [
        {
          "counter": "close_session_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Mcacp policy for all 24 tools.

Get this rule live on your own Mcacp server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MCACP →

View all 24 tools →

These attack patterns abuse exactly the kind of access close_session gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so close_session only ever does what you allow.

SECURE MCACP →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the close_session tool do? +

Close an active session. Session file preserved for future load_session.. It is categorised as a Write tool in the Mcacp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on close_session? +

Register the Mcacp MCP server in PolicyLayer and add a rule for close_session: 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 Mcacp. Nothing to install.

What risk level is close_session? +

close_session is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit close_session? +

Yes. Add a rate_limit block to the close_session 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.

How do I block close_session completely? +

Set action: deny in the PolicyLayer policy for close_session. 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.

What MCP server provides close_session? +

close_session is provided by the Mcacp MCP server (mcacp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcacp tool call.

Deterministic rules across all 24 Mcacp tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.