AI agents use session to create or update resources in Synapsis — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Synapsis environment.
The tool manages session lifecycle including initialization (init), recording observations (observe), and compression (compress), all of which create or modify session state. While 'context' and 'summarize' are read-like, the overall tool is primarily Write as it creates and mutates durable session memory. No evidence of irreversible deletion, code execution, or financial operations.
From the tool's definition Session lifecycle: init | observe | context | summarize | compress | tasks
Attacks that exploit this kind of access
Session lifecycle: init | observe | context | summarize | compress | tasks. It is categorised as a Write tool in the Synapsis MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Synapsis MCP server in PolicyLayer and add a rule for 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 Synapsis. Nothing to install.
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 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 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.
session is provided by the Synapsis MCP server (teamolimpo/synapsis). 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 →