debug_network_connectivity
AI agents call debug_network_connectivity to retrieve information from Looker Admin MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the lack of description, network diagnostics typically retrieve status information without side effects. The tool appears designed to test or verify connectivity state, which is a read-only activity. However, confidence is moderate due to the empty description—debug tools could theoretically trigger network operations.
From the tool's definition Tool name is 'debug_network_connectivity' with no description provided. The 'debug' prefix and 'connectivity' check suggest diagnostic/observational functionality rather than modification or execution of external operations.
Attacks that exploit this kind of access
debug_network_connectivity. It is categorised as a Read tool in the Looker Admin MCP MCP Server, which means it retrieves data without modifying state.
Register the Looker Admin MCP server in PolicyLayer and add a rule for debug_network_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 Looker Admin MCP. Nothing to install.
debug_network_connectivity 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 debug_network_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.
Set action: deny in the PolicyLayer policy for debug_network_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.
debug_network_connectivity is provided by the Looker Admin MCP server (kokevidaurre/looker-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →