sp_analyze

Analyze HTML and recommend which stitch-pro tools to run. Detects accessibility issues, missing responsiveness, framework conversion opportunities, and component library mapping potential.

ServerStitch Pro
CategoryRead

How to control sp_analyze ↓

WHAT IT DOES

What sp_analyze does on Stitch Pro

AI agents call sp_analyze to retrieve information from Stitch Pro without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

THE RISK

Low Risk

Why sp_analyze needs a policy

sp_analyze inspects HTML input to identify issues and suggest next steps, with no side effects. It queries/examines data (accessibility, responsiveness, conversion opportunities) and returns findings/recommendations. This is a standard diagnostic/advisory tool with no capability to execute code, modify data, delete resources, or trigger external operations.

From the tool's definition Tool description states it "Analyze[s] HTML and recommend[s]" — purely analytical/detection operations with no modification, deletion, execution, or financial impact. Keywords: 'Analyze', 'Detects', 'recommend' indicate read-only inspection.

Documented attack patterns abuse exactly the kind of access sp_analyze gives an agent:

POLICY

How to control sp_analyze

PolicyLayer is an MCP gateway — it sits between your AI agents and Stitch Pro, and nothing reaches the server without passing your rules. This is the rule we recommend for sp_analyze:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sp_analyze": {}
  }
}

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

Create a free account and register Stitch Pro — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Stitch Pro tools

Execute sp_a11y Run WCAG 2.1 AA accessibility audit on HTML and auto-fix issues (contrast, semantics, ARIA Execute sp_auto Describe what you want in plain English. Automatically chains design system creation, page Execute sp_to_svelte Convert HTML/Tailwind to SvelteKit components with Svelte 5 runes ($state) and optional co Execute sp_to_vue Convert HTML/Tailwind to Vue 3 Single File Components with Composition API and optional co Execute sp_smart_convert Converts HTML to a framework, but auto-detects if it needs accessibility fixes and respons Write sp_flow Generate multiple related screens (e.g., login → dashboard → settings) in one call with co Write sp_responsive Make HTML responsive by injecting Tailwind breakpoints for mobile, tablet, and desktop Write sp_to_react Convert HTML/Tailwind to Next.js/React components with proper state, props, hooks, and opt

All 17 Stitch Pro tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about sp_analyze

What does the sp_analyze tool do? +

Analyze HTML and recommend which stitch-pro tools to run. Detects accessibility issues, missing responsiveness, framework conversion opportunities, and component library mapping potential. It is categorised as a Read tool in the Stitch Pro MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on sp_analyze? +

Register the Stitch Pro MCP server in PolicyLayer and add a rule for sp_analyze: 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 Stitch Pro. Nothing to install.

What risk level is sp_analyze? +

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

Can I rate-limit sp_analyze? +

Yes. Add a rate_limit block to the sp_analyze 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 sp_analyze completely? +

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

sp_analyze is provided by the Stitch Pro MCP server (luciferdono/stitch-pro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Stitch Pro tool call.

Start from Stitch Pro, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

17 Stitch Pro tools catalogued and risk-classified — across an index of 43,000+ MCP servers.