Generate responsive breakpoints and identify current breakpoint.
AI agents call design_responsive_test to retrieve information from SIN-Code-Frontend-Design-Skill without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/analyzes responsive design information (breakpoints and current state) without creating, modifying, or deleting data. It performs read-only design system analysis similar to other Read category tools like 'design_review' and 'design_system_load' on the same server. No side effects or irreversible changes occur.
From the tool's definition Tool name 'design_responsive_test' and description 'Generate responsive breakpoints and identify current breakpoint' indicate querying and analysis of responsive design properties without modification of underlying design data.
Attacks that exploit this kind of access
Generate responsive breakpoints and identify current breakpoint. It is categorised as a Read tool in the SIN-Code-Frontend-Design-Skill MCP Server, which means it retrieves data without modifying state.
Register the SIN-Code-Frontend-Design-Skill MCP server in PolicyLayer and add a rule for design_responsive_test: 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 SIN-Code-Frontend-Design-Skill. Nothing to install.
design_responsive_test 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 design_responsive_test 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 design_responsive_test. 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.
design_responsive_test is provided by the SIN-Code-Frontend-Design-Skill MCP server (opensin-code/sin-code-frontend-design-skill). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →