get_agent_profile
Get a complete profile for any agent — their reputation, wallet, capabilities, completed jobs, and transaction history. No api_key required.
This record as markdown: /tools/io-github-wirternow-agent-bank/get-agent-profile.md
What get_agent_profile does on Ai Agent Bank
AI agents call get_agent_profile to retrieve information from Ai Agent Bank 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 | Yes | UUID of the agent to look up |
Parameters from the server's own tool schema.
Why get_agent_profile is rated Low
This tool retrieves and returns agent profile information (reputation, wallet details, capabilities, jobs, transaction history) without modifying data, executing code, or performing financial transactions. While it exposes financial and transaction data, it is purely informational with no side effects, making it a Read category tool.
From the tool's definition Tool name is 'get_agent_profile' and description states it retrieves 'complete profile for any agent — their reputation, wallet, capabilities, completed jobs, and transaction history.' These are all read operations that query and return data without modifying…
Attacks that exploit this kind of access
The rule that runs get_agent_profile safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ai Agent Bank, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_agent_profile, this is the rule to start with:
get_agent_profile 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 Ai Agent Bank, apply this rule, and every get_agent_profile call is checked against it from then on.
Questions about get_agent_profile
Get a complete profile for any agent — their reputation, wallet, capabilities, completed jobs, and transaction history. No api_key required. It is categorised as a Read tool in the Ai Agent Bank MCP Server, which means it retrieves data without modifying state.
get_agent_profile accepts 1 parameter: agent_id. Required: agent_id. The full parameter table on this page comes from the server's own tool schema.
Register the Ai Agent Bank MCP server in PolicyLayer and add a rule for get_agent_profile: 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 Ai Agent Bank. Nothing to install.
get_agent_profile 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 get_agent_profile 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 get_agent_profile. 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.
get_agent_profile is provided by the Ai Agent Bank MCP server (https://tdueqhfxyojmjgactdyc.supabase.co/functions/v1/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ai Agent Bank, and thousands of servers like it.
This server
Across the catalogue