Clears highlights and ghosting in the open viewer.
AI agents use viewer_clear to create or update resources in PyNet Bridge — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PyNet Bridge environment.
This tool modifies the state of the viewer UI by removing visual elements (highlights and ghosting). It is reversible since highlights/ghosting can be reapplied. It does not delete data, execute code, or perform financial operations, making Write the most appropriate category. Severity is low as it only affects visual presentation in a viewer.
From the tool's definition Clears highlights and ghosting in the open viewer
Attacks that exploit this kind of access
Clears highlights and ghosting in the open viewer. It is categorised as a Write tool in the PyNet Bridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PyNet Bridge MCP server in PolicyLayer and add a rule for viewer_clear: 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_clear is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the viewer_clear 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_clear. 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_clear 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 →