Scans the system for running Autodesk processes with an active PyNet IPC pipe.
AI agents call list_active_instances 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 passive discovery and enumeration of running processes. It has no side effects, does not execute code, does not modify state, and does not delete or create resources. The worst-case misuse scenario is information disclosure about what Autodesk processes are running, which is low severity and typical of read operations. Classification as Read is appropriate.
From the tool's definition Tool description states it 'Scans the system for running Autodesk processes' — a read-only query operation that retrieves status information about active processes without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Scans the system for running Autodesk processes with an active PyNet IPC pipe. 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 list_active_instances: 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.
list_active_instances 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 list_active_instances 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 list_active_instances. 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.
list_active_instances 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 →