reputation_get_last_index

Get the last feedback index submitted by a specific client for an agent.

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-get-last-index.md

WHAT IT DOES

What reputation_get_last_index does on Aibtc

AI agents call reputation_get_last_index 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_get_last_index is rated Low

This tool retrieves historical feedback information about a client-agent interaction. It performs a query without altering data or triggering external operations. The read-only nature and limited scope (feedback metadata retrieval) indicate low severity and low risk of misuse.

From the tool's definition Tool name contains 'get' and description states 'Get the last feedback index submitted by a specific client for an agent' — a straightforward data retrieval operation with no modification, deletion, or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs reputation_get_last_index 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_last_index, this is the rule to start with:

reputation_get_last_index Allowed

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

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_get_last_index call is checked against it from then on.

FAQ

Questions about reputation_get_last_index

What does the reputation_get_last_index tool do? +

Get the last feedback index submitted by a specific client for an agent. 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_get_last_index? +

Register the Aibtc MCP server in PolicyLayer and add a rule for reputation_get_last_index: 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_get_last_index? +

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

Can I rate-limit reputation_get_last_index? +

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

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

reputation_get_last_index 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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