run_javascript
Execute JavaScript in a Safari tab. Use list_tabs to find window/tab indices. Returns the result as a string.
This record as markdown: /tools/io-github-heznpc-iconnect/run-javascript.md
What run_javascript does on Iconnect
AI agents invoke run_javascript to trigger actions in Iconnect. 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 run_javascript is rated High
This tool directly executes code (JavaScript) in a browser context, which can access sensitive information, manipulate web pages, trigger network requests, and interact with user data. The high severity reflects that JavaScript execution in Safari can access localStorage, cookies, DOM state, and potentially exfiltrate data or perform unwanted actions on any website loaded in that tab.
From the tool's definition Tool explicitly states 'Execute JavaScript in a Safari tab' with ability to run code and return results.
Attacks that exploit this kind of access
The rule that runs run_javascript safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_javascript, this is the rule to start with:
run_javascript 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 Iconnect, apply this rule, and every run_javascript call is checked against it from then on.
Questions about run_javascript
Execute JavaScript in a Safari tab. Use list_tabs to find window/tab indices. Returns the result as a string. It is categorised as a Execute tool in the Iconnect MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Iconnect MCP server in PolicyLayer and add a rule for run_javascript: 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 Iconnect. Nothing to install.
run_javascript 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 run_javascript 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 run_javascript. 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.
run_javascript is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
Across the catalogue