Save authentication cookies for a website. Opens a browser
AI agents use save_authentication to create or update resources in WebClone MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WebClone MCP Server environment.
This tool creates and persists authentication state (cookies/sessions) which are reversible but represent unauthorized credential persistence if misused by an AI agent. An agent could save stolen session cookies for websites it doesn't own, enabling account takeover or unauthorized access.
From the tool's definition The tool 'save_authentication' with description 'Save authentication cookies for a website. Opens a browser' creates and stores new authentication credentials/sessions. The server description mentions 'manage authentication sessions' as a capability.
Documented attack patterns abuse exactly the kind of access save_authentication gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WebClone MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for save_authentication:
{
"version": "1",
"default": "deny",
"tools": {
"save_authentication": {
"limits": [
{
"counter": "save_authentication_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}save_authentication 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.
Save authentication cookies for a website. Opens a browser. It is categorised as a Write tool in the WebClone MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WebClone MCP Server MCP server in PolicyLayer and add a rule for save_authentication: 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 WebClone MCP Server. Nothing to install.
save_authentication 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 save_authentication 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 save_authentication. 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.
save_authentication is provided by the WebClone MCP Server MCP server (ruslanmv/webclone). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WebClone MCP Server, 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.
5 WebClone MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.