Mark a single discovered URL as processed after the agent has handled it. Sets processed_at to the current timestamp and stores the result for audit trail. Idempotent — calling on an already-processed URL updates the fields. Use cases: - Mark a URL as
AI agents use mark_discovered_url_processed to create or update resources in Playwright Stealth — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Playwright Stealth environment.
This tool modifies data (marking URLs and updating timestamps) but does not destroy data, execute code, move money, or trigger external operations with uncontrolled side effects. The operation is reversible—a URL's processed state can be changed again. The scope is narrow (a single URL record) with minimal blast radius. Idempotency reduces risk further.
From the tool's definition Tool updates records by setting 'processed_at' to current timestamp and stores results. Description explicitly states it 'Mark a single discovered URL as processed' and 'updates the fields', indicating reversible modification of data state.
Documented attack patterns abuse exactly the kind of access mark_discovered_url_processed gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Playwright Stealth, and nothing reaches the server without passing your rules. This is the rule we recommend for mark_discovered_url_processed:
{
"version": "1",
"default": "deny",
"tools": {
"mark_discovered_url_processed": {
"limits": [
{
"counter": "mark_discovered_url_processed_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}mark_discovered_url_processed 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.
Mark a single discovered URL as processed after the agent has handled it. Sets processed_at to the current timestamp and stores the result for audit trail. Idempotent — calling on an already-processed URL updates the fields. Use cases: - Mark a URL as. It is categorised as a Write tool in the Playwright Stealth MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Playwright Stealth MCP server in PolicyLayer and add a rule for mark_discovered_url_processed: 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 Playwright Stealth. Nothing to install.
mark_discovered_url_processed 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 mark_discovered_url_processed 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 mark_discovered_url_processed. 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.
mark_discovered_url_processed is provided by the Playwright Stealth MCP server (pulsemcp/mcp-servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Playwright Stealth, 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.
68 Playwright Stealth tools catalogued and risk-classified — across an index of 43,000+ MCP servers.