Request a feature or format that Caliper doesn't support yet. Free, no payment required. Use this when you need a capability that Caliper doesn't currently offer — especially unsupported file formats (STEP, IGES) or analysis features not yet available. Requests are logged and used to prioritize d...
Part of the Caliper server.
Free to start. No card required.
AI agents call feature_request to retrieve information from Caliper without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though feature_request only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"feature_request": {}
}
}See the full Caliper policy for all 10 tools.
These attack patterns abuse exactly the kind of access feature_request gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Request a feature or format that Caliper doesn't support yet. Free, no payment required. Use this when you need a capability that Caliper doesn't currently offer — especially unsupported file formats (STEP, IGES) or analysis features not yet available. Requests are logged and used to prioritize development. Privacy policy: https://caliper.fit/privacy. It is categorised as a Read tool in the Caliper MCP Server, which means it retrieves data without modifying state.
Register the Caliper MCP server in PolicyLayer and add a rule for feature_request: 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 Caliper. Nothing to install.
feature_request 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 feature_request 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 feature_request. 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.
feature_request is provided by the Caliper MCP server (https://caliper.fit/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 Caliper tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.