Low Risk

get_session_info

Get information about the current Pro Tools session (name, path, sample rate)

How to control get_session_info ↓

What get_session_info does on Pro Tools MCP Server

AI agents call get_session_info to retrieve information from Pro Tools MCP Server 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_info needs a policy

This is a pure query operation that retrieves metadata about an active session without creating, modifying, deleting, or executing any actions. It has minimal blast radius—an AI agent cannot misuse session metadata retrieval to cause harm. Classified as Read with low severity.

From the tool's definition Tool name 'get_session_info' and description state it retrieves information about the current Pro Tools session (name, path, sample rate) with no modification or side effects.

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

How to control get_session_info

PolicyLayer is an MCP gateway — it sits between your AI agents and Pro Tools MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_session_info:

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

get_session_info 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 Pro Tools MCP Server — 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_info

What does the get_session_info tool do? +

Get information about the current Pro Tools session (name, path, sample rate). It is categorised as a Read tool in the Pro Tools MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_session_info? +

Register the Pro Tools MCP Server MCP server in PolicyLayer and add a rule for get_session_info: 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 Pro Tools MCP Server. Nothing to install.

What risk level is get_session_info? +

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

Can I rate-limit get_session_info? +

Yes. Add a rate_limit block to the get_session_info 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_info completely? +

Set action: deny in the PolicyLayer policy for get_session_info. 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_info? +

get_session_info is provided by the Pro Tools MCP Server MCP server (skrul/protools-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Pro Tools MCP Server tool call.

Start from Pro Tools MCP Server, 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.

36 Pro Tools MCP Server 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.