AI agents call paste_text as a supporting operation in Noapi Google Search workflows.
With no description available, the tool's behavior can only be loosely inferred from its name. 'paste_text' could mean pasting text into a browser field (Execute), writing data somewhere (Write), or something else entirely. Given the server context (headless Chromium, search, media tools), it may interact with a browser input field, but this is speculative.
From the tool's definition Tool name is 'paste_text' and description is empty or uninformative.
Documented attack patterns abuse exactly the kind of access paste_text gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Noapi Google Search, and nothing reaches the server without passing your rules. This is the rule we recommend for paste_text:
{
"version": "1",
"default": "deny",
"tools": {
"paste_text": {
"limits": [
{
"counter": "paste_text_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}paste_text gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
paste_text. It is categorised as a Other tool in the Noapi Google Search MCP Server, which means it performs auxiliary operations.
Register the Noapi Google Search MCP server in PolicyLayer and add a rule for 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 Noapi Google Search. Nothing to install.
paste_text is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the 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 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.
paste_text is provided by the Noapi Google Search MCP server (vincentkaufmann/noapi-google-search-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 38 Noapi Google Search tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
38 Noapi Google Search tools catalogued and risk-classified — across an index of 42,500+ MCP servers.