reconnect

Reconnect to the gadget after an app crash.

SERVERFrida Agent MCP SOURCE1193776794/frida-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/1193776794-frida-mcp/reconnect.md

WHAT IT DOES

What reconnect does on Frida Agent MCP

AI agents invoke reconnect to trigger actions in Frida Agent MCP. 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.

RISK

Why reconnect is rated High

Reconnecting to a Frida gadget re-establishes an instrumentation session on a running Android process, triggering external operations against a live process. While it sounds benign, it re-enables dynamic analysis/injection capabilities and interacts with external process state.

From the tool's definition Reconnect to the gadget after an app crash

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs reconnect safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Frida Agent MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reconnect, this is the rule to start with:

reconnect Rate-limited

reconnect 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "reconnect": {
      "limits": [
        {
          "counter": "reconnect_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Frida Agent MCP, apply this rule, and every reconnect call is checked against it from then on.

FAQ

Questions about reconnect

What does the reconnect tool do? +

Reconnect to the gadget after an app crash. It is categorised as a Execute tool in the Frida Agent MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on reconnect? +

Register the Frida Agent MCP server in PolicyLayer and add a rule for reconnect: 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 Frida Agent MCP. Nothing to install.

What risk level is reconnect? +

reconnect is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit reconnect? +

Yes. Add a rate_limit block to the reconnect 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.

How do I block reconnect completely? +

Set action: deny in the PolicyLayer policy for reconnect. 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.

What MCP server provides reconnect? +

reconnect is provided by the Frida Agent MCP server (1193776794/frida-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Frida Agent, and thousands of servers like it.

This server

All 10 Frida Agent tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →