This record as markdown: /tools/kiln/community-stats.md
What community_stats does on Kiln
AI agents call community_stats 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 community_stats is rated Low
The tool name strongly implies a read-only operation that aggregates or retrieves community statistics. With no description provided, confidence is moderately reduced, but the lack of action verbs (create, delete, execute, pay) and the contextual domain (3D printer control systems) suggest this is informational retrieval with no side effects.
From the tool's definition Tool name 'community_stats' suggests retrieval of statistical data; description is empty. Based on naming convention alone, this appears to query community-level metrics rather than perform modifications, deletions, or external operations.
Attacks that exploit this kind of access
The rule that runs community_stats 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 community_stats, this is the rule to start with:
community_stats 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 community_stats call is checked against it from then on.
Questions about community_stats
community_stats 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 community_stats: 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.
community_stats 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 community_stats 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 community_stats. 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.
community_stats 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