New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

revise_script

AI-rewrite a passage of the active script in the project's narrative voice (the same in-editor revise the UI offers). selected_text must appear verbatim in the script; omit it to revise the whole script. Synchronous — returns {revised_text}, which is NOT saved: splice it over selected_text (or re...

SERVERFramesail SOURCEhttps://api.framesail.com/mcp
Medium RISK CLASS
Category Write
Parameters 32 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-framesail-framesail/revise-script.md

What revise_script does on Framesail

AI agents use revise_script to create or update resources in Framesail, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Framesail environment.

ParameterTypeRequiredDescription
project_id string Yes Project ID, as returned by create_project or list_projects
instruction string Yes Natural-language edit instruction, e.g. "make the intro punchier"
selected_text string Exact passage to rewrite; must appear verbatim in the active script. Omit to revise the whole script

Parameters from the server's own tool schema.

Why revise_script is rated Medium

This tool creates or modifies script content reversibly. Although it performs AI-based text rewriting, the changes are not persisted unless the user explicitly saves them via save_script, making this a Write operation rather than Execute. The user retains full control over whether modifications are accepted.

From the tool's definition Tool description states it returns revised_text which is 'NOT saved' and requires explicit call to 'save_script to keep it.' The tool itself performs an AI-based modification of script content, making it a write operation that modifies (reversibly, since…

Questions about revise_script

What does the revise_script tool do? +

AI-rewrite a passage of the active script in the project's narrative voice (the same in-editor revise the UI offers). selected_text must appear verbatim in the script; omit it to revise the whole script. Synchronous — returns {revised_text}, which is NOT saved: splice it over selected_text (or replace the full script) and call save_script to keep it. It is categorised as a Write tool in the Framesail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does revise_script accept? +

revise_script accepts 3 parameters: project_id, instruction, selected_text. Required: project_id, instruction. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on revise_script? +

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

What risk level is revise_script? +

revise_script is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit revise_script? +

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

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

revise_script 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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Framesail's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.