Create a new persistent session rule (stored in Memory MCP)
AI agents use create_session_rule to create or update resources in MCP Conductor — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Conductor environment.
This tool creates and persists new session rules, which are configuration objects that govern AI agent behavior within orchestrated sessions. While the action is reversible (rules can typically be deleted or modified), it modifies system state with potentially wide impact on conversation flow, context access, and agent constraints.
From the tool's definition Tool name 'create_session_rule' and description 'Create a new persistent session rule (stored in Memory MCP)' indicate irreversible data creation. The tool modifies session state by writing rules to persistent storage (Memory MCP).
Documented attack patterns abuse exactly the kind of access create_session_rule gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Conductor, and nothing reaches the server without passing your rules. This is the rule we recommend for create_session_rule:
{
"version": "1",
"default": "deny",
"tools": {
"create_session_rule": {
"limits": [
{
"counter": "create_session_rule_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_session_rule 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.
Free to start. No card required.
Create a new persistent session rule (stored in Memory MCP). It is categorised as a Write tool in the MCP Conductor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Conductor MCP server in PolicyLayer and add a rule for create_session_rule: 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 MCP Conductor. Nothing to install.
create_session_rule 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_rule 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_rule. 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_rule is provided by the MCP Conductor MCP server (lutherscottgarcia/mcp-conductor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Conductor, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
25 MCP Conductor tools catalogued and risk-classified — across an index of 43,000+ MCP servers.