reputation_read_feedback

Read a specific feedback entry for an agent by index from the ERC-8004 reputation registry.

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/reputation-read-feedback.md

WHAT IT DOES

What reputation_read_feedback does on Aibtc

AI agents call reputation_read_feedback to retrieve information from Aibtc without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why reputation_read_feedback is rated Low

The tool retrieves existing feedback data from a registry without modifying, deleting, or executing any operations. Reading feedback entries has minimal risk as it only exposes information already stored in the registry. No financial, destructive, or execution-based actions occur.

From the tool's definition Tool name contains 'read' and description explicitly states 'Read a specific feedback entry...from the ERC-8004 reputation registry.' This is a data retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs reputation_read_feedback safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reputation_read_feedback, this is the rule to start with:

reputation_read_feedback Allowed

reputation_read_feedback 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": {
    "reputation_read_feedback": {}
  }
}

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

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

FAQ

Questions about reputation_read_feedback

What does the reputation_read_feedback tool do? +

Read a specific feedback entry for an agent by index from the ERC-8004 reputation registry. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on reputation_read_feedback? +

Register the Aibtc MCP server in PolicyLayer and add a rule for reputation_read_feedback: 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 Aibtc. Nothing to install.

What risk level is reputation_read_feedback? +

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

Can I rate-limit reputation_read_feedback? +

Yes. Add a rate_limit block to the reputation_read_feedback 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 reputation_read_feedback completely? +

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

reputation_read_feedback is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Aibtc, and thousands of servers like it.

This server

All 358 Aibtc tools →

Across the catalogue

claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

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