This record as markdown: /tools/kiln/marketplace-status.md
What marketplace_status does on Kiln
AI agents call marketplace_status to retrieve information from Kiln without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why marketplace_status is rated Low
The tool name indicates a status check of a marketplace (likely related to 3D printer supplies, spools, or services). The empty description significantly limits confidence. Given the sibling tools context (add_spool, add_assembly_part, etc.), this appears to be a read-only query into marketplace or availability data. No evidence suggests data modification, deletion, code execution, or financial operations.
From the tool's definition Tool name 'marketplace_status' suggests a status query operation, typical of Read category tools that retrieve information without side effects.
Attacks that exploit this kind of access
The rule that runs marketplace_status 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 marketplace_status, this is the rule to start with:
marketplace_status is read-only, so it stays allowed. 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 marketplace_status call is checked against it from then on.
Questions about marketplace_status
marketplace_status is a read tool on the Kiln MCP server. 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 marketplace_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 Kiln. Nothing to install.
marketplace_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 marketplace_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 marketplace_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.
marketplace_status 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