Paste text directly (without typing). Faster than type_text and works with special characters/emojis.
AI agents invoke bytebot_paste_text to trigger actions in ByteBot MCP Server. 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.
This tool inputs text into the desktop environment via clipboard paste, which is a direct desktop control action (keyboard/input operation). It can be misused to inject malicious text into active applications, terminal windows, or forms. The server description explicitly mentions 'direct desktop computer control' and 'mouse/keyboard operations'.
From the tool's definition Paste text directly (without typing). Faster than type_text and works with special characters/emojis.
Attacks that exploit this kind of access
Paste text directly (without typing). Faster than type_text and works with special characters/emojis. It is categorised as a Execute tool in the ByteBot MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ByteBot MCP Server MCP server in PolicyLayer and add a rule for bytebot_paste_text: 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 ByteBot MCP Server. Nothing to install.
bytebot_paste_text 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 bytebot_paste_text 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 bytebot_paste_text. 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.
bytebot_paste_text is provided by the ByteBot MCP Server MCP server (sensuslab/spark-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →