启动设备上的 frida-server。 - 来源: 使用 config.json 的 server_path/server_name/server_port - 返回: {status, path, port, message}
AI agents invoke start_frida_server to trigger actions in Frida. 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.
This tool triggers an external operation (starting a system service/daemon on an Android device) whose effects enable subsequent code execution and instrumentation capabilities. While the action itself is not destructive or financial, it initiates a service that facilitates Execute-class operations (script injection, app manipulation).
From the tool's definition Tool description indicates 'start_frida_server' starts the Frida server on a device. Frida is a dynamic instrumentation framework that allows code injection, function hooking, and runtime manipulation of Android applications.
Documented attack patterns abuse exactly the kind of access start_frida_server gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Frida, and nothing reaches the server without passing your rules. This is the rule we recommend for start_frida_server:
{
"version": "1",
"default": "deny",
"tools": {
"start_frida_server": {
"limits": [
{
"counter": "start_frida_server_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}start_frida_server 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.
启动设备上的 frida-server。 - 来源: 使用 config.json 的 server_path/server_name/server_port - 返回: {status, path, port, message}. It is categorised as a Execute tool in the Frida MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Frida MCP server in PolicyLayer and add a rule for start_frida_server: 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. Nothing to install.
start_frida_server 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 start_frida_server 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 start_frida_server. 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.
start_frida_server is provided by the Frida MCP server (zhizhuodemao/frida-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Frida tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 Frida tools catalogued and risk-classified — across an index of 42,500+ MCP servers.