Gets the JavaScript call stack that initiated a network request. This helps trace which code triggered an API call.
AI agents call get_request_initiator to retrieve information from MiniApp CDP MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool falls into the Read category as it queries execution context information without side effects. Severity is medium because call stack data can reveal implementation details and help an attacker understand WeChat MiniApp architecture, API endpoints, and authentication mechanisms—useful for reverse engineering.
From the tool's definition Tool retrieves call stack information for a network request ("trace which code triggered an API call"). No modification, deletion, or execution of code is performed—only querying and reading debugging data from Chrome DevTools Protocol.
Documented attack patterns abuse exactly the kind of access get_request_initiator gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MiniApp CDP MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_request_initiator:
{
"version": "1",
"default": "deny",
"tools": {
"get_request_initiator": {}
}
}get_request_initiator is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Gets the JavaScript call stack that initiated a network request. This helps trace which code triggered an API call. It is categorised as a Read tool in the MiniApp CDP MCP MCP Server, which means it retrieves data without modifying state.
Register the MiniApp CDP MCP server in PolicyLayer and add a rule for get_request_initiator: 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 MiniApp CDP MCP. Nothing to install.
get_request_initiator is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_request_initiator 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 get_request_initiator. 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.
get_request_initiator is provided by the MiniApp CDP MCP server (zhizhuodemao/miniapp-cdp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 18 MiniApp CDP MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
18 MiniApp CDP MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.