issue_shipping_confirmation_token
A write tool on the Kiln MCP server.
This record as markdown: /tools/kiln/issue-shipping-confirmation-token.md
What issue_shipping_confirmation_token does on Kiln
AI agents use issue_shipping_confirmation_token to create or update resources in Kiln, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kiln environment.
Why issue_shipping_confirmation_token is rated Medium
An AI agent can call issue_shipping_confirmation_token faster than any human can review: one bad instruction and it creates or modifies resources in Kiln by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs issue_shipping_confirmation_token safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Kiln, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For issue_shipping_confirmation_token, this is the rule to start with:
issue_shipping_confirmation_token stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Kiln, apply this rule, and every issue_shipping_confirmation_token call is checked against it from then on.
Questions about issue_shipping_confirmation_token
issue_shipping_confirmation_token is a write tool on the Kiln MCP server. It is categorised as a Write tool in the Kiln MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kiln MCP server in PolicyLayer and add a rule for issue_shipping_confirmation_token: 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.
issue_shipping_confirmation_token is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the issue_shipping_confirmation_token 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 issue_shipping_confirmation_token. 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.
issue_shipping_confirmation_token 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.
More on Kiln, and thousands of servers like it.
This server
Across the catalogue