eval_page
Run JavaScript in the device page (use it to repair selectors)
This record as markdown: /tools/0click-insta/eval-page.md
What eval_page does on 0click Insta
AI agents invoke eval_page to trigger actions in 0click Insta. 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.
Why eval_page is rated High
eval_page triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs eval_page safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0click Insta, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For eval_page, this is the rule to start with:
eval_page 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.
The button opens the PolicyLayer dashboard: create your workspace, connect 0click Insta, apply this rule, and every eval_page call is checked against it from then on.
Questions about eval_page
Run JavaScript in the device page (use it to repair selectors). It is categorised as a Execute tool in the 0click Insta MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the 0click Insta MCP server in PolicyLayer and add a rule for eval_page: 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 0click Insta. Nothing to install.
eval_page 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 eval_page 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 eval_page. 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.
eval_page is provided by the 0click Insta MCP server (akufikri/0click-insta). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0click Insta, and thousands of servers like it.
Across the catalogue