AI agents use archive_webpage to create or update resources in Noapi Google Search — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Noapi Google Search environment.
The name 'archive_webpage' suggests saving or storing a webpage, which is a Write operation. However, with no description available, confidence is low. It could involve fetching (Read) or submitting to an archive service (Write/Execute). Given the most common interpretation — saving/archiving a page to some storage — Write is the best guess. Severity is medium as misuse could store unintended content.
From the tool's definition Tool name 'archive_webpage' — description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access archive_webpage 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 archive_webpage:
{
"version": "1",
"default": "deny",
"tools": {
"archive_webpage": {
"limits": [
{
"counter": "archive_webpage_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}archive_webpage 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.
archive_webpage. It is categorised as a Write tool in the Noapi Google Search MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Noapi Google Search MCP server in PolicyLayer and add a rule for archive_webpage: 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.
archive_webpage 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 archive_webpage 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 archive_webpage. 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.
archive_webpage 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.