Simulate a design token change without actually applying it. Perfect for design reviews and impact planning.
AI agents call simulate_token_change 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 retrieves and analyzes the impact of a hypothetical design token change without creating, modifying, or deleting any data. It is purely informational for planning purposes. The 'simulate' framing and explicit 'without actually applying' language confirm it has no persistent effects.
From the tool's definition Tool name includes 'simulate' and description explicitly states 'without actually applying it' — the operation performs analysis and preview only, with no side effects or state modifications.
Documented attack patterns abuse exactly the kind of access simulate_token_change 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 simulate_token_change:
{
"version": "1",
"default": "deny",
"tools": {
"simulate_token_change": {}
}
}simulate_token_change 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.
Simulate a design token change without actually applying it. Perfect for design reviews and impact planning. 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 simulate_token_change: 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.
simulate_token_change 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 simulate_token_change 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 simulate_token_change. 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.
simulate_token_change 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.