Check if a proposed action complies with session rules
AI agents call enforce_session_rules to retrieve information from MCP Conductor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool description uses 'Check if', indicating a read/validation operation that evaluates a proposed action against existing session rules. It does not modify, execute, or delete anything — it merely returns a compliance verdict. Severity is low because misuse would at worst produce incorrect compliance assessments, not direct data modification or destruction.
From the tool's definition 'Check if a proposed action complies with session rules' — the tool checks/validates compliance, implying a read/query operation with no side effects
Documented attack patterns abuse exactly the kind of access enforce_session_rules 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 enforce_session_rules:
{
"version": "1",
"default": "deny",
"tools": {
"enforce_session_rules": {}
}
} enforce_session_rules is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check if a proposed action complies with session rules. It is categorised as a Read tool in the MCP Conductor MCP Server, which means it retrieves data without modifying state.
Register the MCP Conductor MCP server in PolicyLayer and add a rule for enforce_session_rules: 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.
enforce_session_rules is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the enforce_session_rules 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 enforce_session_rules. 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.
enforce_session_rules 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.