check_connection
AI agents call check_connection to retrieve information from Figma MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'check_connection' indicates a read-only operation that verifies connectivity without modifying, executing, or deleting any data. It has no side effects and serves an informational purpose. The lack of a description lowers confidence slightly, but the semantic meaning of the name strongly suggests a passive diagnostic operation typical of connection validation patterns in API clients.
From the tool's definition Tool name 'check_connection' with empty description suggests a status check or diagnostic operation. Based on naming convention and context of a Figma MCP server, this appears to be a connection validation utility.
Attacks that exploit this kind of access
check_connection. It is categorised as a Read tool in the Figma MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Figma MCP Server MCP server in PolicyLayer and add a rule for check_connection: 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 Figma MCP Server. Nothing to install.
check_connection 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 check_connection 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 check_connection. 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.
check_connection is provided by the Figma MCP Server MCP server (sichang824/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 →