AI agents call diagnose_connection to retrieve information from Xugu without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Diagnosing connection issues is a read/inspection operation that checks connectivity status without modifying data or executing commands. It retrieves diagnostic information about the database connection state.
From the tool's definition Diagnose database connection issues
Attacks that exploit this kind of access
Diagnose database connection issues. It is categorised as a Read tool in the Xugu MCP Server, which means it retrieves data without modifying state.
Register the Xugu MCP server in PolicyLayer and add a rule for diagnose_connection: 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 Xugu. Nothing to install.
diagnose_connection 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 diagnose_connection 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 diagnose_connection. 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.
diagnose_connection is provided by the Xugu MCP server (leokupo/xugu-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 →