analyze_style
Re-run style analysis (after changing a style's inputs). Async — await_jobs(style_id=...) until the style_analysis job completes.
This record as markdown: /tools/com-framesail-framesail/analyze-style.md
What analyze_style does on Framesail
AI agents invoke analyze_style to trigger actions in Framesail. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
style_id | string | Yes | ID of the style to re-analyze, from create_style or list_styles |
Parameters from the server's own tool schema.
Why analyze_style is rated High
The tool triggers an asynchronous analysis job on a remote system, which constitutes executing an external operation. It is not a simple read (it re-runs processing) and not purely write (it produces derived analytical results via a job pipeline). The blast radius is medium since misuse could waste compute resources or corrupt style analysis state, but it does not directly delete data or move money.
From the tool's definition "Re-run style analysis" and "Async — await_jobs(style_id=...) until the style_analysis job completes" indicate triggering an external asynchronous job/operation
Attacks that exploit this kind of access
The rule that runs analyze_style safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Framesail, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For analyze_style, this is the rule to start with:
analyze_style stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Framesail, apply this rule, and every analyze_style call is checked against it from then on.
Questions about analyze_style
Re-run style analysis (after changing a style's inputs). Async — await_jobs(style_id=...) until the style_analysis job completes. It is categorised as a Execute tool in the Framesail MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
analyze_style accepts 1 parameter: style_id. Required: style_id. The full parameter table on this page comes from the server's own tool schema.
Register the Framesail MCP server in PolicyLayer and add a rule for analyze_style: 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 Framesail. Nothing to install.
analyze_style is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the analyze_style 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 analyze_style. 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.
analyze_style is provided by the Framesail MCP server (https://api.framesail.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Framesail, and thousands of servers like it.
Across the catalogue