Low Risk

get_paused_info

Gets information about the current paused state including call stack, current location, and scope variables. Use this after a breakpoint is hit to understand the execution context.

How to control get_paused_info ↓

AI agents call get_paused_info 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.

Low Risk

This tool is Read category because it retrieves and queries data (call stack, current location, scope variables) with no side effects or state modifications. However, severity is medium rather than low because in the context of reverse engineering WeChat MiniApp code (as stated in server description), access to scope variables and call stacks could reveal sensitive application logic, credentials, or proprietary…

From the tool's definition get_paused_info retrieves information about paused execution state including call stack, location, and scope variables. It performs queries on debugger state without modification or execution.

Documented attack patterns abuse exactly the kind of access get_paused_info 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_paused_info:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_paused_info": {}
  }
}

get_paused_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MiniApp CDP MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_paused_info tool do? +

Gets information about the current paused state including call stack, current location, and scope variables. Use this after a breakpoint is hit to understand the execution context. It is categorised as a Read tool in the MiniApp CDP MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_paused_info? +

Register the MiniApp CDP MCP server in PolicyLayer and add a rule for get_paused_info: 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.

What risk level is get_paused_info? +

get_paused_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_paused_info? +

Yes. Add a rate_limit block to the get_paused_info 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 get_paused_info completely? +

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

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

Enforce policy on every MiniApp CDP MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.