Check if CSM.ai integration is enabled in Blender.
AI agents call get_csm_status to retrieve information from BlenderMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves state information about whether CSM.ai integration is active. It performs a query with no data modification, execution of arbitrary code, deletion, or financial impact. The blast radius of misuse is minimal—an agent could only learn whether a feature is enabled, which poses no security risk.
From the tool's definition Tool name 'get_csm_status' and description 'Check if CSM.ai integration is enabled in Blender' indicate a status query with no side effects. The verb 'Check' and the informational nature of retrieving integration status are consistent with Read operations.
Attacks that exploit this kind of access
Check if CSM.ai integration is enabled in Blender. It is categorised as a Read tool in the BlenderMCP MCP Server, which means it retrieves data without modifying state.
Register the Blender MCP server in PolicyLayer and add a rule for get_csm_status: 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 BlenderMCP. Nothing to install.
get_csm_status 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_csm_status 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_csm_status. 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_csm_status is provided by the Blender MCP server (richard-devbot/blender-mcp-csm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →