get_design_spec
Return the full design governance specification as structured JSON. Includes: approved semantic colors, typography classes and uppercase policy, component layout primitives, spacing scale, button classes, focus ring pattern, motion rules, border radius rules, and all banned patterns with fix sugg...
This record as markdown: /tools/io-github-homenshum-nodebench/get-design-spec.md
What get_design_spec does on Nodebench
AI agents call get_design_spec to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_design_spec is rated Low
This tool retrieves design specification data as structured JSON for reference purposes. It has no side effects, does not create, modify, delete, or execute any operations. The data it returns informs subsequent UI development decisions but does not itself perform any mutations or external actions.
From the tool's definition Tool description states 'Return the full design governance specification' and explicitly instructs to 'Use this before writing or modifying UI code' — it retrieves and queries design system data without modifying it.
Attacks that exploit this kind of access
The rule that runs get_design_spec safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_design_spec, this is the rule to start with:
get_design_spec is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every get_design_spec call is checked against it from then on.
Questions about get_design_spec
Return the full design governance specification as structured JSON. Includes: approved semantic colors, typography classes and uppercase policy, component layout primitives, spacing scale, button classes, focus ring pattern, motion rules, border radius rules, and all banned patterns with fix suggestions. Use this before writing or modifying UI code to ensure compliance. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for get_design_spec: 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 Nodebench. Nothing to install.
get_design_spec 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_design_spec 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_design_spec. 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_design_spec is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue