get_script
Read the active script's full text + the version list. Use this to show the script to your user for review/feedback before scan_script — the review-edit-resave loop (get_script -> discuss -> save_script) is the expected workflow when the user wants input.
This record as markdown: /tools/com-framesail-framesail/get-script.md
What get_script does on Framesail
AI agents call get_script to retrieve information from Framesail without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
project_id | string | Yes | Project ID, as returned by create_project or list_projects |
Parameters from the server's own tool schema.
Why get_script is rated Low
This tool retrieves and displays script content and version history without modifying, creating, deleting, or executing anything. It is a pure read operation with no blast radius—the worst outcome is stale or incorrect information presented to a user. It fits squarely in the Read category with low severity.
From the tool's definition Tool name is 'get_script' and description states 'Read the active script's full text + the version list'. The verb 'Read' explicitly indicates data retrieval.
Attacks that exploit this kind of access
The rule that runs get_script 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 get_script, this is the rule to start with:
get_script 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 Framesail, apply this rule, and every get_script call is checked against it from then on.
Questions about get_script
Read the active script's full text + the version list. Use this to show the script to your user for review/feedback before scan_script — the review-edit-resave loop (get_script -> discuss -> save_script) is the expected workflow when the user wants input. It is categorised as a Read tool in the Framesail MCP Server, which means it retrieves data without modifying state.
get_script accepts 1 parameter: project_id. Required: project_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 get_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.
get_script 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_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.
Set action: deny in the PolicyLayer policy for get_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.
get_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.
This server
Across the catalogue