send_instance_takeover_input
Send ONE mouse or keyboard event into a taken-over page (relayed to the real browser over CDP). This is the raw remote-control primitive the console
This record as markdown: /tools/io-github-proagentstore-platform/send-instance-takeover-input.md
What send_instance_takeover_input does on ProAgentStore
AI agents invoke send_instance_takeover_input to trigger actions in ProAgentStore. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why send_instance_takeover_input is rated High
Directly controls a remote browser via CDP, executing arbitrary input actions.
From the tool's definition Send ONE mouse or keyboard event into a taken-over page
Attacks that exploit this kind of access
The rule that runs send_instance_takeover_input safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ProAgentStore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For send_instance_takeover_input, this is the rule to start with:
send_instance_takeover_input stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ProAgentStore, apply this rule, and every send_instance_takeover_input call is checked against it from then on.
Questions about send_instance_takeover_input
Send ONE mouse or keyboard event into a taken-over page (relayed to the real browser over CDP). This is the raw remote-control primitive the console. It is categorised as a Execute tool in the ProAgentStore MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ProAgentStore MCP server in PolicyLayer and add a rule for send_instance_takeover_input: 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 ProAgentStore. Nothing to install.
send_instance_takeover_input is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the send_instance_takeover_input 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 send_instance_takeover_input. 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.
send_instance_takeover_input is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ProAgentStore, and thousands of servers like it.
Across the catalogue