AI agents call query_compatibility to retrieve information from Netlab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reports compatibility information from netlab's declarations and lab observations. It performs a lookup or query operation with no side effects, no code execution, no data modification, and no destructive actions. It is purely informational, making it a Read category tool with low severity risk.
From the tool's definition Tool description states it queries/retrieves what netlab 'declares' a platform supports and what was 'observed' in the lab.
Attacks that exploit this kind of access
What netlab *declares* a platform supports, overlaid with what was *observed* in the lab. It is categorised as a Read tool in the Netlab MCP Server, which means it retrieves data without modifying state.
Register the Netlab MCP server in PolicyLayer and add a rule for query_compatibility: 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 Netlab. Nothing to install.
query_compatibility 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 query_compatibility 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 query_compatibility. 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.
query_compatibility is provided by the Netlab MCP server (steinzi/netlab-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 →