spine_info

Use this to inspect Spine project, JSON, binary skeleton, or folder metadata through the Spine CLI. Do not use it to export, modify, pack, or open projects.

SERVERSpine SOURCE1425sd/spine-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/1425sd-spine-mcp/spine-info.md

WHAT IT DOES

What spine_info does on Spine

AI agents call spine_info 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.

RISK

Why spine_info is rated Low

The tool is explicitly limited to inspection and metadata retrieval with no side effects. The description explicitly forbids modification or export actions, confirming this is a read-only operation.

From the tool's definition 'inspect Spine project, JSON, binary skeleton, or folder metadata' and 'Do not use it to export, modify, pack, or open projects'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs spine_info 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_info, this is the rule to start with:

spine_info Allowed

spine_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "spine_info": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Spine, apply this rule, and every spine_info call is checked against it from then on.

FAQ

Questions about spine_info

What does the spine_info tool do? +

Use this to inspect Spine project, JSON, binary skeleton, or folder metadata through the Spine CLI. Do not use it to export, modify, pack, or open projects. It is categorised as a Read tool in the Spine MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on spine_info? +

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

What risk level is spine_info? +

spine_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit spine_info? +

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

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

spine_info 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.

KEEP EXPLORING

More on Spine, and thousands of servers like it.

This server

All 16 Spine tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →