identity_get_last_id

Get the most recently minted agent ID from the ERC-8004 identity 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/identity-get-last-id.md

WHAT IT DOES

What identity_get_last_id does on Aibtc

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

This tool queries data (an agent ID) from a registry without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name contains 'get' and description states 'Get the most recently minted agent ID from the ERC-8004 identity registry' — a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

identity_get_last_id Allowed

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

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

FAQ

Questions about identity_get_last_id

What does the identity_get_last_id tool do? +

Get the most recently minted agent ID from the ERC-8004 identity 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 identity_get_last_id? +

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

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

Can I rate-limit identity_get_last_id? +

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

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

identity_get_last_id 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 →