Return the local WebSocket bridge status and active Figma plugin connection details.
AI agents call figma_connection_status to retrieve information from MC Figma Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a status-check operation that retrieves information about the active connection state without side effects. It poses minimal risk as it cannot modify Figma documents, execute operations, or affect system state beyond returning metadata about an existing connection.
From the tool's definition Tool returns connection status and details without modifying any data; described as 'Return the local WebSocket bridge status and active Figma plugin connection details' indicating query/retrieval only.
Attacks that exploit this kind of access
Return the local WebSocket bridge status and active Figma plugin connection details. It is categorised as a Read tool in the MC Figma Bridge MCP Server, which means it retrieves data without modifying state.
Register the MC Figma Bridge MCP server in PolicyLayer and add a rule for figma_connection_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 MC Figma Bridge. Nothing to install.
figma_connection_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 figma_connection_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 figma_connection_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.
figma_connection_status is provided by the MC Figma Bridge MCP server (mochammad123/mcp-figma). 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 →