server_info

THE RISK

Low Risk

Why server_info needs a policy

This tool only retrieves metadata about the server (version, status, info). It is a pure read/query operation with no side effects and minimal blast radius if misused.

From the tool's definition Return Blender MCP server information, version, and status

Documented attack patterns abuse exactly the kind of access server_info gives an agent:

POLICY

How to control server_info

PolicyLayer is an MCP gateway — it sits between your AI agents and Blender, and nothing reaches the server without passing your rules. This is the rule we recommend for server_info:

policy.json

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

server_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Blender — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Blender tools

Destructive clear_scene Remove all objects from the current scene. Execute blender_transform blender_transform Execute script_execute Execute Python script in Blender (headless). Execute agentic_blender_workflow agentic_blender_workflow Execute blender_animation blender_animation Execute blender_geonodes blender_geonodes Execute blender_jobs Async job queue for long-running Blender Python scripts (renders, bakes, sims). Execute blender_particles blender_particles

All 77 Blender tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about server_info

What does the server_info tool do? +

Return Blender MCP server information, version, and status. It is categorised as a Read tool in the Blender MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on server_info? +

Register the Blender MCP server in PolicyLayer and add a rule for server_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 Blender. Nothing to install.

What risk level is server_info? +

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

Can I rate-limit server_info? +

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

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

server_info is provided by the Blender MCP server (sandraschi/blender-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Blender tool call.

Start from Blender, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →