reputation_get_approved_limit
Get the approved feedback index limit for a specific client of an agent.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/reputation-get-approved-limit.md
What reputation_get_approved_limit does on Aibtc
AI agents call reputation_get_approved_limit 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.
Why reputation_get_approved_limit is rated Low
This tool queries state information (an approval limit) for a given client. It is purely informational and does not modify, execute operations, or affect financial or destructive outcomes. The 'Get' verb and read-only semantics confirm Read category with low severity.
From the tool's definition Tool name contains 'get' and description states 'Get the approved feedback index limit' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs reputation_get_approved_limit 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_get_approved_limit, this is the rule to start with:
reputation_get_approved_limit 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 Aibtc, apply this rule, and every reputation_get_approved_limit call is checked against it from then on.
Questions about reputation_get_approved_limit
Get the approved feedback index limit for a specific client of an agent. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.
Register the Aibtc MCP server in PolicyLayer and add a rule for reputation_get_approved_limit: 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.
reputation_get_approved_limit 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 reputation_get_approved_limit 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 reputation_get_approved_limit. 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.
reputation_get_approved_limit 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.
More on Aibtc, and thousands of servers like it.
This server
Across the catalogue