Low Risk

get_session_rules

Retrieve all active session rules

How to control get_session_rules ↓

What get_session_rules does on MCP Conductor

AI agents call get_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.

Low Risk

Why get_session_rules needs a policy

This tool retrieves session rules without modifying, deleting, or executing any operations. It performs a query/fetch operation with no side effects. The worst-case misuse would be an AI agent reading session rule configurations to understand access patterns, which poses minimal risk compared to tools that can modify rules or execute operations.

From the tool's definition Tool name 'get_session_rules' and description 'Retrieve all active session rules' indicate a read-only operation that queries existing session rule configuration.

Documented attack patterns abuse exactly the kind of access get_session_rules gives an agent:

How to control get_session_rules

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 get_session_rules:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_session_rules": {}
  }
}

get_session_rules is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MCP Conductor — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_session_rules

What does the get_session_rules tool do? +

Retrieve all active session rules. It is categorised as a Read tool in the MCP Conductor MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_session_rules? +

Register the MCP Conductor MCP server in PolicyLayer and add a rule for get_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.

What risk level is get_session_rules? +

get_session_rules is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_session_rules? +

Yes. Add a rate_limit block to the get_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.

How do I block get_session_rules completely? +

Set action: deny in the PolicyLayer policy for get_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.

What MCP server provides get_session_rules? +

get_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.

Enforce policy on every MCP Conductor tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.