This record as markdown: /tools/frontmcp/set-session-data.md
What set-session-data does on Frontmcp
AI agents use set-session-data to create or update resources in Frontmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Frontmcp environment.
Why set-session-data is rated Medium
This tool writes data to a session object, which is a reversible operation. While session data modification could affect subsequent requests or expose sensitive information if misused, it does not permanently delete data (not Destructive), move money (not Financial), or execute arbitrary code (not Execute).
From the tool's definition Tool name contains 'set' and description states 'Store data in the session', indicating the tool creates or modifies session-scoped data.
Attacks that exploit this kind of access
The rule that runs set-session-data safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set-session-data, this is the rule to start with:
set-session-data stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Frontmcp, apply this rule, and every set-session-data call is checked against it from then on.
Questions about set-session-data
Store data in the session. It is categorised as a Write tool in the Frontmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Front MCP server in PolicyLayer and add a rule for set-session-data: 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 Frontmcp. Nothing to install.
set-session-data 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 set-session-data 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 set-session-data. 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.
set-session-data is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Front, and thousands of servers like it.
This server
Across the catalogue