Get this agent's identity info. Returns the server's DID, public key, name, and capabilities.
AI agents call get_identity to retrieve information from Agentos without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves identity metadata (DID, public key, name, capabilities) about the agent without creating, modifying, deleting, or executing any operations. It is purely informational and has no blast radius if misused by an agent—the worst outcome is that identity information is read when it perhaps shouldn't be. This is a standard Read operation.
From the tool's definition Tool description states 'Get this agent's identity info' and 'Returns the server's DID, public key, name, and capabilities.' The verb 'Get' and 'Returns' indicate retrieval of existing metadata with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_identity gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agentos, and nothing reaches the server without passing your rules. This is the rule we recommend for get_identity:
{
"version": "1",
"default": "deny",
"tools": {
"get_identity": {}
}
} get_identity is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get this agent's identity info. Returns the server's DID, public key, name, and capabilities. It is categorised as a Read tool in the Agentos MCP Server, which means it retrieves data without modifying state.
Register the Agentos MCP server in PolicyLayer and add a rule for get_identity: 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 Agentos. Nothing to install.
get_identity 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_identity 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_identity. 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_identity is provided by the Agentos MCP server (@microsoft/agentos-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Agentos, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 Agentos tools catalogued and risk-classified — across an index of 43,000+ MCP servers.