Reports whether a PyNet BIM Viewer is open in VS Code (port, package, data dir).
AI agents call viewer_status 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 retrieves current state information (port, package, data directory) about a running PyNet BIM Viewer without altering any data or triggering side effects. It is a pure read operation with minimal security impact—the returned information could reveal system configuration details, but cannot be exploited to modify, delete, or execute code.
From the tool's definition Tool name 'viewer_status' and description 'Reports whether a PyNet BIM Viewer is open in VS Code' indicate a query operation that retrieves status information about an open viewer. No modification, deletion, execution, or financial operations are performed.
Attacks that exploit this kind of access
Reports whether a PyNet BIM Viewer is open in VS Code (port, package, data dir). 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_status: 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_status 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_status 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_status. 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_status 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 →