AI agents call get_speed_profile to retrieve information from Kiln without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix strongly indicates a query or retrieval operation with no side effects. The empty description limits confidence, but the naming convention and context of retrieving printer speed configuration parameters align with the Read category. No indication of destructive, financial, or execution capabilities. Severity is low because querying speed profiles poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'get_speed_profile' follows a read-only 'get_' naming pattern, and based on the server's context (3D printer control), a speed profile is configuration/state data that would be retrieved rather than modified.
Attacks that exploit this kind of access
get_speed_profile. It is categorised as a Read tool in the Kiln MCP Server, which means it retrieves data without modifying state.
Register the Kiln MCP server in PolicyLayer and add a rule for get_speed_profile: 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 Kiln. Nothing to install.
get_speed_profile 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_speed_profile 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_speed_profile. 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_speed_profile is provided by the Kiln MCP server (codeofaxel/Kiln). 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 →