hiveagent_rep_score
Get an agent's full reputation: trust score (0-100), credit score (300-850), tier (bronze→diamond), badges, and transaction history.
This record as markdown: /tools/hiveagentiq-hiveagent/hiveagent-rep-score.md
What hiveagent_rep_score does on Hiveagent
AI agents call hiveagent_rep_score to retrieve information from Hiveagent 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 |
|---|---|---|---|
agent_id | string | — |
Parameters from the server's own tool schema.
Why hiveagent_rep_score is rated Low
This tool only fetches existing reputation information about agents. No data is created, modified, deleted, or executed. However, the reputation data could include transaction history and financial metrics (credit score 300-850), which are sensitive in an agent economy context.
From the tool's definition Tool retrieves and queries an agent's reputation data: 'trust score', 'credit score', 'tier', 'badges', and 'transaction history'. The verb is 'Get' and the action is read-only retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs hiveagent_rep_score safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hiveagent, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hiveagent_rep_score, this is the rule to start with:
hiveagent_rep_score 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 Hiveagent, apply this rule, and every hiveagent_rep_score call is checked against it from then on.
Questions about hiveagent_rep_score
Get an agent's full reputation: trust score (0-100), credit score (300-850), tier (bronze→diamond), badges, and transaction history. It is categorised as a Read tool in the Hiveagent MCP Server, which means it retrieves data without modifying state.
hiveagent_rep_score accepts 1 parameter: agent_id. The full parameter table on this page comes from the server's own tool schema.
Register the Hiveagent MCP server in PolicyLayer and add a rule for hiveagent_rep_score: 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 Hiveagent. Nothing to install.
hiveagent_rep_score 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 hiveagent_rep_score 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 hiveagent_rep_score. 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.
hiveagent_rep_score is provided by the Hiveagent MCP server (hiveagentiq/hiveagent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hiveagent, and thousands of servers like it.
This server
Across the catalogue