Reads the loaded package's clashes.json — the data source, NOT the viewer/IFC.
AI agents call viewer_list_clashes to retrieve information from PyNet Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that retrieves and lists clash data from a JSON file. It has no side effects, does not modify data, execute code, delete resources, or involve financial operations. The low severity reflects minimal blast radius if misused by an AI agent—it can only expose existing clash data without causing harm.
From the tool's definition Tool name includes 'list' and description states it 'Reads the loaded package's clashes.json' with explicit clarification that it accesses 'the data source, NOT the viewer/IFC'.
Attacks that exploit this kind of access
Reads the loaded package's clashes.json — the data source, NOT the viewer/IFC. It is categorised as a Read tool in the PyNet Bridge MCP Server, which means it retrieves data without modifying state.
Register the PyNet Bridge MCP server in PolicyLayer and add a rule for viewer_list_clashes: 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 PyNet Bridge. Nothing to install.
viewer_list_clashes 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 viewer_list_clashes 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 viewer_list_clashes. 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.
viewer_list_clashes is provided by the PyNet Bridge MCP server (rafael-nunezdearenas/pynetbridge). 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 →