Debug tool to check what tokens are currently stored in the design token registry
AI agents call debug_token_registry to retrieve information from Sunnyside Figma MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs inspection and querying of stored design tokens without modifying, deleting, or executing any operations. It is a diagnostic read operation that retrieves state information from a registry. The blast radius of misuse is minimal - at worst, an AI agent could gain visibility into design token structure, but cannot alter designs, execute code, or cause destructive effects.
From the tool's definition Tool described as 'Debug tool to check what tokens are currently stored in the design token registry' - uses 'check' language indicating data retrieval/inspection without modification or side effects.
Documented attack patterns abuse exactly the kind of access debug_token_registry gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sunnyside Figma MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for debug_token_registry:
{
"version": "1",
"default": "deny",
"tools": {
"debug_token_registry": {}
}
}debug_token_registry is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Debug tool to check what tokens are currently stored in the design token registry. It is categorised as a Read tool in the Sunnyside Figma MCP MCP Server, which means it retrieves data without modifying state.
Register the Sunnyside Figma MCP server in PolicyLayer and add a rule for debug_token_registry: 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 Sunnyside Figma MCP. Nothing to install.
debug_token_registry 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 debug_token_registry 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 debug_token_registry. 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.
debug_token_registry is provided by the Sunnyside Figma MCP server (tercumantanumut/sunnysidefigma-context-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 31 Sunnyside Figma MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
31 Sunnyside Figma MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.