check_burp_connectivity · Burp Suite MCP Server MCP

WHAT IT DOES

What check_burp_connectivity does on Burp Suite MCP Server

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

WHY IT NEEDS A POLICY

Why check_burp_connectivity needs a policy

Connectivity checks are non-invasive diagnostic operations that retrieve status information without triggering scans, modifying data, or executing arbitrary code. This aligns with the Read category. Severity is low because even if the tool fails or is misused, it poses minimal security risk—it cannot access sensitive data, trigger actions, or affect system state.

From the tool's definition Tool name 'check_burp_connectivity' indicates a status check operation. The empty description limits direct evidence, but the naming convention and context within a Burp Suite integration suggest this performs a connection test or health check—a read-only…

Attacks that exploit this kind of access

Questions about check_burp_connectivity

What does the check_burp_connectivity tool do? +

check_burp_connectivity. It is categorised as a Read tool in the Burp Suite MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_burp_connectivity? +

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

What risk level is check_burp_connectivity? +

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

Can I rate-limit check_burp_connectivity? +

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

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

check_burp_connectivity is provided by the Burp Suite MCP Server MCP server (jayluxferro/burp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.