Low Risk

track_design_system_health

Monitor design system health over time. Identifies token drift, unused tokens, inconsistent usage patterns.

How to control track_design_system_health ↓

AI agents call track_design_system_health 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.

Low Risk

This tool performs observational analysis of design tokens and their usage patterns. It retrieves and examines existing data (token drift, unused tokens, usage patterns) but does not create, modify, delete, or execute external operations. The verbs 'monitor' and 'identifies' indicate read-only introspection of the design system state. No side effects or irreversible actions are possible.

From the tool's definition Tool description states it 'Monitor[s] design system health over time. Identifies token drift, unused tokens, inconsistent usage patterns' — all query/analysis operations with no modification or deletion of data.

Documented attack patterns abuse exactly the kind of access track_design_system_health 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 track_design_system_health:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "track_design_system_health": {}
  }
}

track_design_system_health is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Sunnyside Figma MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the track_design_system_health tool do? +

Monitor design system health over time. Identifies token drift, unused tokens, inconsistent usage patterns. It is categorised as a Read tool in the Sunnyside Figma MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on track_design_system_health? +

Register the Sunnyside Figma MCP server in PolicyLayer and add a rule for track_design_system_health: 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.

What risk level is track_design_system_health? +

track_design_system_health is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit track_design_system_health? +

Yes. Add a rate_limit block to the track_design_system_health 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.

How do I block track_design_system_health completely? +

Set action: deny in the PolicyLayer policy for track_design_system_health. 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.

What MCP server provides track_design_system_health? +

track_design_system_health 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.

Enforce policy on every Sunnyside Figma MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.