Low Risk

debug_issue

Get debugging guidance for React Native issues

How to control debug_issue ↓

What debug_issue does on React Native MCP Server

AI agents call debug_issue to retrieve information from React Native MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why debug_issue needs a policy

This tool retrieves and returns debugging guidance/advice for React Native issues. It is a read/query operation that provides informational output without modifying any state, executing code, or causing side effects. It's analogous to a search or lookup operation for debugging recommendations.

From the tool's definition "Get debugging guidance for React Native issues" - purely provides guidance/information

Documented attack patterns abuse exactly the kind of access debug_issue gives an agent:

How to control debug_issue

PolicyLayer is an MCP gateway — it sits between your AI agents and React Native MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for debug_issue:

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

debug_issue 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 React Native MCP Server — 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.

Related tools and policies

Go deeper

Questions about debug_issue

What does the debug_issue tool do? +

Get debugging guidance for React Native issues. It is categorised as a Read tool in the React Native MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on debug_issue? +

Register the React Native MCP Server MCP server in PolicyLayer and add a rule for debug_issue: 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 React Native MCP Server. Nothing to install.

What risk level is debug_issue? +

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

Can I rate-limit debug_issue? +

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

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

debug_issue is provided by the React Native MCP Server MCP server (mrnitro360/react-native-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every React Native MCP Server tool call.

Start from React Native MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

17 React Native MCP Server tools catalogued and risk-classified — across an index of 43,000+ 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.