Generate a playbook JSON from your session. Extracts URLs, selectors, errors+solutions from memory. Share the output with ScreenHand to help others automate this platform.
AI agents use export_playbook to create or update resources in ScreenHand — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ScreenHand environment.
This tool writes/creates new data (playbook JSON files) by synthesizing session information. It does not execute commands, delete data, or move financial resources. The output is reversible—exported playbooks can be discarded or updated. The severity is low because exporting automation playbooks has minimal blast radius; the worst case is cluttered file systems or sharing of public/non-sensitive automation workflows.
From the tool's definition The tool 'Generate a playbook JSON from your session' and 'Share the output' indicates it creates structured data artifacts (playbook files) from session history. It extracts information and exports it, which are creation/write operations.
Documented attack patterns abuse exactly the kind of access export_playbook gives an agent:
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 export_playbook:
{
"version": "1",
"default": "deny",
"tools": {
"export_playbook": {
"limits": [
{
"counter": "export_playbook_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_playbook stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Generate a playbook JSON from your session. Extracts URLs, selectors, errors+solutions from memory. Share the output with ScreenHand to help others automate this platform. It is categorised as a Write tool in the ScreenHand MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ScreenHand MCP server in PolicyLayer and add a rule for export_playbook: 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.
export_playbook is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the export_playbook 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 export_playbook. 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.
export_playbook 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.
Start from ScreenHand, 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.
89 ScreenHand tools catalogued and risk-classified — across an index of 43,000+ MCP servers.