Trigger reload in Metro bundler
AI agents invoke reload_metro to trigger actions in MCP Connect. 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.
reload_metro performs an Execute action by triggering an external operation (Metro bundler reload) rather than simply reading data (Read) or making reversible modifications (Write). The tool invokes an external process with side effects on the Metro development server. While this is reversible (unlike Destructive actions), it qualifies as Execute because it runs an external command/operation.
From the tool's definition Tool description explicitly states 'Trigger reload in Metro bundler', which is an external operation that initiates a process. Metro is the JavaScript bundler used by React Native.
Attacks that exploit this kind of access
Trigger reload in Metro bundler. It is categorised as a Execute tool in the MCP Connect MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Connect MCP server in PolicyLayer and add a rule for reload_metro: 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 MCP Connect. Nothing to install.
reload_metro 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 reload_metro 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 reload_metro. 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.
reload_metro is provided by the MCP Connect MCP server (plaintest/mcp-connect). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →