check_reputation
Check reputation score of an agent
This record as markdown: /tools/io-github-bbrainfrance-midas-protocol/check-reputation.md
What check_reputation does on MIDAS Protocol
AI agents call check_reputation to retrieve information from MIDAS Protocol without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
agentId | string | Yes |
Parameters from the server's own tool schema.
Why check_reputation is rated Low
This tool retrieves information (a reputation score) about another agent. It performs no write, execution, deletion, or financial operation. Despite the financial context of the MIDAS Protocol server, this specific tool is a read-only lookup operation with minimal risk if misused by an AI agent.
From the tool's definition Tool name 'check_reputation' and description 'Check reputation score of an agent' indicate a query/lookup operation that retrieves reputation data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs check_reputation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MIDAS Protocol, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_reputation, this is the rule to start with:
check_reputation 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 MIDAS Protocol, apply this rule, and every check_reputation call is checked against it from then on.
Questions about check_reputation
Check reputation score of an agent. It is categorised as a Read tool in the MIDAS Protocol MCP Server, which means it retrieves data without modifying state.
check_reputation accepts 1 parameter: agentId. Required: agentId. The full parameter table on this page comes from the server's own tool schema.
Register the MIDAS Protocol MCP server in PolicyLayer and add a rule for check_reputation: 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 MIDAS Protocol. Nothing to install.
check_reputation 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 check_reputation 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 check_reputation. 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.
check_reputation is provided by the MIDAS Protocol MCP server (https://mcp.midasprotocol.org/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MIDAS Protocol, and thousands of servers like it.
This server
Across the catalogue