Create a new session context snapshot.
AI agents use create_session_context to create or update resources in Session Buddy — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Session Buddy environment.
The tool creates new session context snapshots, which modifies the session state by adding records. This is reversible (snapshots can be deleted or overwritten) and has no destructive or financial implications. It does not execute arbitrary code or read existing data, so Write is the correct classification.
From the tool's definition Tool name 'create_session_context' and description 'Create a new session context snapshot' indicate creation of session data records. Verb 'create' and noun 'snapshot' show data creation without deletion, placing this in the Write category.
Attacks that exploit this kind of access
Create a new session context snapshot. It is categorised as a Write tool in the Session Buddy MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Session Buddy MCP server in PolicyLayer and add a rule for create_session_context: 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 Session Buddy. Nothing to install.
create_session_context 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 create_session_context 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 create_session_context. 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.
create_session_context is provided by the Session Buddy MCP server (lesleslie/session-buddy). 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 →