AI agents use create_star to create or update resources in Claude Talk to Figma MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Talk to Figma MCP environment.
The tool creates new graphical elements (stars) in a Figma design document. This is reversible via undo and does not execute arbitrary code or delete data, placing it in the Write category. Severity is medium because misuse could clutter or degrade a design project, but the impact is limited to adding a single design element and can be easily undone.
From the tool's definition Tool name 'create_star' and description 'Create a new star in Figma' indicate the tool creates a new design element in Figma. This is a write operation that modifies the design file by adding content.
Documented attack patterns abuse exactly the kind of access create_star gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Talk to Figma MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create_star:
{
"version": "1",
"default": "deny",
"tools": {
"create_star": {
"limits": [
{
"counter": "create_star_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_star stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new star in Figma. It is categorised as a Write tool in the Claude Talk to Figma MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Talk to Figma MCP server in PolicyLayer and add a rule for create_star: 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 Claude Talk to Figma MCP. Nothing to install.
create_star is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_star 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 create_star. 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.
create_star is provided by the Claude Talk to Figma MCP server (arinspunk/claude-talk-to-figma-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Talk to Figma MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
93 Claude Talk to Figma MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.