Get the history of dev code extractions from the Figma plugin
AI agents call get_figma_dev_history 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 is a read-only operation that retrieves audit/history logs of previous code extraction activities. It has no side effects, does not execute code, does not modify design files or tokens, and does not affect any external systems. The blast radius of misuse is minimal—an agent could only view historical extraction records, not alter designs or trigger new operations.
From the tool's definition The tool 'get_figma_dev_history' retrieves historical data about code extractions ('Get the history of dev code extractions'). It queries past operations without modifying, deleting, or executing anything.
Documented attack patterns abuse exactly the kind of access get_figma_dev_history 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 get_figma_dev_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_figma_dev_history": {}
}
}get_figma_dev_history 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.
Get the history of dev code extractions from the Figma plugin. 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 get_figma_dev_history: 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.
get_figma_dev_history 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 get_figma_dev_history 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 get_figma_dev_history. 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.
get_figma_dev_history 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.