Update session metadata (display name, timeout). Supports dry-run mode.
AI agents use acp_update_session to create or update resources in Ambient Code Platform MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ambient Code Platform MCP Server environment.
The tool updates session metadata (display name, timeout) which are reversible modifications to session state. This is a Write operation rather than Destructive since metadata changes can be undone.
From the tool's definition Tool name 'acp_update_session' and description states it 'Update[s] session metadata (display name, timeout)'. This modifies existing session configuration reversibly.
Attacks that exploit this kind of access
Update session metadata (display name, timeout). Supports dry-run mode. It is categorised as a Write tool in the Ambient Code Platform MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ambient Code Platform MCP Server MCP server in PolicyLayer and add a rule for acp_update_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 Ambient Code Platform MCP Server. Nothing to install.
acp_update_session 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 acp_update_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.
Set action: deny in the PolicyLayer policy for acp_update_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.
acp_update_session is provided by the Ambient Code Platform MCP Server MCP server (jeremyeder/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 →