AI agents call get_known_good 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 queries and retrieves existing, pre-validated network configurations and topology data. It performs a lookup operation without modifying, deleting, executing code, or triggering external actions. The primary function is informational—providing reference configurations that have already been tested. There is no risk of unintended side effects, data corruption, or irreversible changes.
From the tool's definition Tool name 'get_known_good' and description 'Return a previously lab-passed topology + rendered config' indicate retrieval of stored data with no side effects. Uses passive verb 'return' and accesses pre-existing validated configurations from a lab database.
Attacks that exploit this kind of access
Return a previously lab-passed topology + rendered config for module+platform, if any. 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 get_known_good: 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.
get_known_good 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 get_known_good 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 get_known_good. 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.
get_known_good 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 →