Lists all script buttons for a specific module ID.
AI agents call get_buttons_data 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 information about script buttons associated with a module. The verb 'Lists' and the read-only nature of the operation (fetching data without modification, deletion, or execution) clearly place this in the Read category. There is minimal risk from misuse—an AI agent listing buttons poses no security threat. Severity is low as the operation only retrieves metadata about UI elements.
From the tool's definition Tool name 'get_buttons_data' and description 'Lists all script buttons for a specific module ID' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
Lists all script buttons for a specific module ID. 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_buttons_data: 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_buttons_data 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_buttons_data 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_buttons_data. 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_buttons_data 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 →