get_session_info

THE RISK

Low Risk

Why get_session_info needs a policy

This tool retrieves and queries session metadata without creating, modifying, deleting, or executing anything. It has no side effects on the browser session or external systems. The blast radius of misuse is minimal—an agent could learn details about existing sessions but cannot harm data or systems through this operation alone.

From the tool's definition Tool description explicitly states 'Get detailed information about a specific browser session' — a retrieval operation with no modification. Actions listed (uptime, current URL, console logs, activity metrics) are all read-only queries.

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

POLICY

How to control get_session_info

PolicyLayer is an MCP gateway — it sits between your AI agents and RunAutomation 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.

Create a free account and register RunAutomation MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More RunAutomation MCP Server tools

Destructive clear_codegen_session Clear a code generation session without generating a test Destructive cleanup_idle_sessions Automatically close idle browser sessions that haven Destructive close_browser_session Close a specific browser session and cleanup all resources including browser instance, pag Destructive playwright_close Close the browser and release all resources Execute playwright_delete Perform an HTTP DELETE request Execute playwright_batch_ai_visual_compare Run batch AI visual comparisons across multiple pages Execute playwright_emulate_device Emulate a mobile device with specific viewport, user agent, and capabilities. Supports all Execute playwright_evaluate Execute JavaScript in the browser console

All 91 RunAutomation MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_session_info

What does the get_session_info tool do? +

Get detailed information about a specific browser session including uptime, current URL, console logs, and activity metrics. It is categorised as a Read tool in the RunAutomation MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_session_info? +

Register the RunAutomation 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 RunAutomation 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 RunAutomation MCP Server MCP server (tayyabakmal1/runautomation-mcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every RunAutomation MCP Server tool call.

Start from RunAutomation MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →