who_am_i

Get your user profile with usage statistics — tier, top tools used, recent activity, saved memories count, and industries researched. Useful for understanding your Adrata context.

SERVERAdrata SOURCE@adrata/adrata-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/adrata-adrata-mcp/who-am-i.md

WHAT IT DOES

What who_am_i does on Adrata

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

RISK

Why who_am_i is rated Low

Even though who_am_i 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 who_am_i safely

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

who_am_i Allowed

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

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

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

FAQ

Questions about who_am_i

What does the who_am_i tool do? +

Get your user profile with usage statistics — tier, top tools used, recent activity, saved memories count, and industries researched. Useful for understanding your Adrata context. It is categorised as a Read tool in the Adrata MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on who_am_i? +

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

What risk level is who_am_i? +

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

Can I rate-limit who_am_i? +

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

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

who_am_i is provided by the Adrata MCP server (@adrata/adrata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Adrata, and thousands of servers like it.

This server

All 278 Adrata tools →

Across the catalogue

The MCP Attack Database →

Guides

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