Get detailed information about a specific CSM.ai session by its session code.
AI agents call get_csm_session_details 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 and queries session information—a read-only operation with no side effects, data modification, execution of code, destructive actions, or financial impact. The 'get' prefix and passive information retrieval nature confirm classification as Read.
From the tool's definition Tool name 'get_csm_session_details' and description 'Get detailed information about a specific CSM.ai session' indicate retrieval of session metadata without modification or execution of operations.
Attacks that exploit this kind of access
Get detailed information about a specific CSM.ai session by its session code. 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_session_details: 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_session_details 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_session_details 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_session_details. 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_session_details 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 →