execution_plan

THE RISK

Low Risk

Why execution_plan needs a policy

This tool only retrieves and displays an execution plan/fallback chain — it does not execute anything, modify data, or trigger external operations. It is purely informational/read-only.

From the tool's definition 'Show the execution plan for an action type. Returns the ordered fallback chain based on available infrastructure.'

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

POLICY

How to control execution_plan

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execution_plan": {}
  }
}

execution_plan 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 ScreenHand — 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 ScreenHand tools

Destructive recording_cancel Cancel the current recording without saving. Destructive watch_unregister Remove a watch rule by ID. Execute applescript Run an AppleScript command. For controlling Finder, Safari, Mail, Notes, etc. (macOS only) Execute app_launch Launch a macOS/Windows application by bundle ID (e.g., Execute browser_js Execute JavaScript in a Chrome/Electron tab. Returns the result. WARNING: This runs arbitr Execute browser_navigate Navigate the active Chrome/Electron tab to a URL Execute browser_wait Wait for a condition on a Chrome/Electron page Execute launch Launch an application by bundle ID

All 89 ScreenHand 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 execution_plan

What does the execution_plan tool do? +

Show the execution plan for an action type. Returns the ordered fallback chain based on available infrastructure. It is categorised as a Read tool in the ScreenHand MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on execution_plan? +

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

What risk level is execution_plan? +

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

Can I rate-limit execution_plan? +

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

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

execution_plan is provided by the ScreenHand MCP server (manushi4/screenhand). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ScreenHand tool call.

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

CHECK YOUR STACK →