spine_get_generation_guide
Use this to load the learned Spine generation guide and machine-readable presets before deciding animation parameters. It reads learned-spine-guide.md, learned-animation-presets.json, and learned-naming-rules.json. If files are missing, run spine_learn_from_corpus first. Do not use it to scan cor...
This record as markdown: /tools/1425sd-spine-mcp/spine-get-generation-guide.md
What spine_get_generation_guide does on Spine
AI agents call spine_get_generation_guide to retrieve information from Spine without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why spine_get_generation_guide is rated Low
This tool only retrieves and loads pre-existing guide and preset data for informational purposes before other operations. It has no capability to modify data, execute code, delete resources, or perform financial transactions. The read-only nature and informational purpose place it unambiguously in the Read category with low severity.
From the tool's definition Tool description states it 'reads' files (learned-spine-guide.md, learned-animation-presets.json, learned-naming-rules.json) and explicitly instructs not to 'scan corpus, call Spine CLI, or build animations'. No side effects or modifications occur.
Attacks that exploit this kind of access
The rule that runs spine_get_generation_guide safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Spine, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For spine_get_generation_guide, this is the rule to start with:
spine_get_generation_guide 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 Spine, apply this rule, and every spine_get_generation_guide call is checked against it from then on.
Questions about spine_get_generation_guide
Use this to load the learned Spine generation guide and machine-readable presets before deciding animation parameters. It reads learned-spine-guide.md, learned-animation-presets.json, and learned-naming-rules.json. If files are missing, run spine_learn_from_corpus first. Do not use it to scan corpus, call Spine CLI, or build animations. It is categorised as a Read tool in the Spine MCP Server, which means it retrieves data without modifying state.
Register the Spine MCP server in PolicyLayer and add a rule for spine_get_generation_guide: 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 Spine. Nothing to install.
spine_get_generation_guide 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 spine_get_generation_guide 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 spine_get_generation_guide. 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.
spine_get_generation_guide is provided by the Spine MCP server (1425sd/spine-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Spine, and thousands of servers like it.
This server
Across the catalogue