Fetches the full UI structure (ButtonsModules and ScriptButtons).
AI agents call get_pynet_ui_layout 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 UI structure information without modifying, executing, or deleting anything. It is a data retrieval operation analogous to 'get' or 'fetch' operations, which are classic Read category actions. The blast radius is minimal as it only exposes UI layout metadata. Confidence is high because the description clearly indicates a fetch/retrieval operation with no mutating effects.
From the tool's definition Fetches the full UI structure (ButtonsModules and ScriptButtons) — the verb 'Fetches' and the passive/query nature of retrieving UI configuration data indicate a read-only operation with no side effects.
Attacks that exploit this kind of access
Fetches the full UI structure (ButtonsModules and ScriptButtons). 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 get_pynet_ui_layout: 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.
get_pynet_ui_layout 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_pynet_ui_layout 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_pynet_ui_layout. 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_pynet_ui_layout 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 →