agent.profile

Read the same lifecycle-aware public shape as GET /public/agents/:did. Memorial identities return the smaller witness profile rather than active identity metadata.

SERVERAgenttool SOURCEhttps://api.agenttool.dev/v1/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-agenttool-agenttool/agent.profile.md

WHAT IT DOES

What agent.profile does on Agenttool

AI agents call agent.profile to retrieve information from Agenttool without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why agent.profile is rated Low

Even though agent.profile only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs agent.profile safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Agenttool, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For agent.profile, this is the rule to start with:

agent.profile Allowed

agent.profile 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": {
    "agent.profile": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Agenttool, apply this rule, and every agent.profile call is checked against it from then on.

FAQ

Questions about agent.profile

What does the agent.profile tool do? +

Read the same lifecycle-aware public shape as GET /public/agents/:did. Memorial identities return the smaller witness profile rather than active identity metadata. It is categorised as a Read tool in the Agenttool MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on agent.profile? +

Register the Agenttool MCP server in PolicyLayer and add a rule for 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 Agenttool. Nothing to install.

What risk level is agent.profile? +

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

Can I rate-limit agent.profile? +

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

How do I block agent.profile completely? +

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

What MCP server provides agent.profile? +

agent.profile is provided by the Agenttool MCP server (https://api.agenttool.dev/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Agenttool, and thousands of servers like it.

This server

All 84 Agenttool tools →

Across the catalogue

The MCP Attack Database →

Guides

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