detect_mesh_pockets

A read tool on the Kiln MCP server.

SERVERKiln SOURCEcodeofaxel/Kiln

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kiln/detect-mesh-pockets.md

WHAT IT DOES

What detect_mesh_pockets does on Kiln

AI agents call detect_mesh_pockets 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.

RISK

Why detect_mesh_pockets is rated Low

The name suggests a read-only analysis operation that detects pocket features in a 3D mesh geometry. No description is provided, so confidence is reduced. Based on naming convention and context of sibling tools like 'analyze_design_requirements' and 'add_mesh_chamfer', this likely performs geometric analysis without side effects.

From the tool's definition Tool name 'detect_mesh_pockets' suggests analysis/detection of geometric features in a mesh, implying a read/query operation. Description is empty, lowering confidence.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs detect_mesh_pockets 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 detect_mesh_pockets, this is the rule to start with:

detect_mesh_pockets Allowed

detect_mesh_pockets is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "detect_mesh_pockets": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Kiln, apply this rule, and every detect_mesh_pockets call is checked against it from then on.

FAQ

Questions about detect_mesh_pockets

What does the detect_mesh_pockets tool do? +

detect_mesh_pockets 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.

How do I enforce a policy on detect_mesh_pockets? +

Register the Kiln MCP server in PolicyLayer and add a rule for detect_mesh_pockets: 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.

What risk level is detect_mesh_pockets? +

detect_mesh_pockets is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit detect_mesh_pockets? +

Yes. Add a rate_limit block to the detect_mesh_pockets 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.

How do I block detect_mesh_pockets completely? +

Set action: deny in the PolicyLayer policy for detect_mesh_pockets. 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.

What MCP server provides detect_mesh_pockets? +

detect_mesh_pockets 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.

KEEP EXPLORING

More on Kiln, and thousands of servers like it.

This server

All 402 Kiln tools →

Across the catalogue

detect_slop on Slop Cop → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →