Low Risk

report_experience

Submit an experience report for a certified capability. Reports feed into the social proof signal of the trust score. Requires the content_hash from the .cert.json artifact (proves you've encountered the certified file). API key optional but recommended for higher rate limits.

High parameter count (13 properties)

Part of the Fidensa MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call report_experience to retrieve information from Fidensa 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 report_experience 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.

fidensa.yaml
tools:
  report_experience:
    rules:
      - action: allow

See the full Fidensa policy for all 7 tools.

Tool Name report_experience
Category Read
MCP Server Fidensa MCP Server
Risk Level Low

Agents calling read-class tools like report_experience have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the report_experience tool do? +

Submit an experience report for a certified capability. Reports feed into the social proof signal of the trust score. Requires the content_hash from the .cert.json artifact (proves you've encountered the certified file). API key optional but recommended for higher rate limits.. It is categorised as a Read tool in the Fidensa MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on report_experience? +

Add a rule in your Intercept YAML policy under the tools section for report_experience. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Fidensa MCP server.

What risk level is report_experience? +

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

Can I rate-limit report_experience? +

Yes. Add a rate_limit block to the report_experience rule in your Intercept 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 report_experience completely? +

Set action: deny in the Intercept policy for report_experience. 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 report_experience? +

report_experience is provided by the Fidensa MCP server (@fidensa/mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Fidensa

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.