get_section_template
Inspect the prompt sections a generation job exposes for per-call override via editable_sections (jobs: script, script_scan, storyboard, segment_image, segment_video, voice_block, ...). Sections marked locked cannot be overridden.
This record as markdown: /tools/com-framesail-framesail/get-section-template.md
What get_section_template does on Framesail
AI agents call get_section_template 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 |
|---|---|---|---|
job | string | Yes | Generation job name, e.g. "script", "script_scan", "storyboard", "segment_image", "segment_video", "voice_block" |
Parameters from the server's own tool schema.
Why get_section_template is rated Low
This tool queries and returns structural information about generation job templates without creating, modifying, deleting, or executing any operations. It is purely informational and has no side effects on the system or data. Low severity due to minimal blast radius if misused—an agent would only retrieve template metadata.
From the tool's definition Tool name 'get_section_template' and description 'Inspect the prompt sections' clearly indicate retrieval of metadata about available prompt sections and their properties (locked/unlocked status).
Attacks that exploit this kind of access
The rule that runs get_section_template 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_section_template, this is the rule to start with:
get_section_template 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_section_template call is checked against it from then on.
Questions about get_section_template
Inspect the prompt sections a generation job exposes for per-call override via editable_sections (jobs: script, script_scan, storyboard, segment_image, segment_video, voice_block, ...). Sections marked locked cannot be overridden. It is categorised as a Read tool in the Framesail MCP Server, which means it retrieves data without modifying state.
get_section_template accepts 1 parameter: job. Required: job. 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_section_template: 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_section_template 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_section_template 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_section_template. 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_section_template 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