Reload the current page. Useful when page state is stale or after changes.
AI agents invoke refresh to trigger actions in Camofox. 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.
Refreshing/reloading a page is a browser action that triggers an external operation — it causes the browser to re-request and re-render the current page, potentially re-submitting forms, re-triggering scripts, or altering session state. This fits the Execute category as it triggers an external operation with effects that depend on the current page context.
From the tool's definition Reload the current page. Useful when page state is stale or after changes.
Documented attack patterns abuse exactly the kind of access refresh gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Camofox, and nothing reaches the server without passing your rules. This is the rule we recommend for refresh:
{
"version": "1",
"default": "deny",
"tools": {
"refresh": {
"limits": [
{
"counter": "refresh_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}refresh stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Reload the current page. Useful when page state is stale or after changes. It is categorised as a Execute tool in the Camofox MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Camofox MCP server in PolicyLayer and add a rule for refresh: 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 Camofox. Nothing to install.
refresh 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 refresh 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 refresh. 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.
refresh is provided by the Camofox MCP server (redf0x1/camofox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 47 Camofox tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
47 Camofox tools catalogued and risk-classified — across an index of 42,500+ MCP servers.