Close an ACM session and quit the application.
AI agents use close_acm to create or update resources in ACM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ACM MCP Server environment.
An AI agent can call close_acm faster than any human can review — one bad instruction and it creates or modifies resources in ACM MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Close an ACM session and quit the application. It is categorised as a Write tool in the ACM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ACM MCP Server MCP server in PolicyLayer and add a rule for close_acm: 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 ACM MCP Server. Nothing to install.
close_acm 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 close_acm 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 close_acm. 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.
close_acm is provided by the ACM MCP Server MCP server (pekosann/acm-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 →