AI agents call danke_profile to retrieve information from Danke without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a lookup/query operation to retrieve profile data about an agent or human. This is a read-only operation with no modifications, financial transactions, or destructive actions. Severity is low as it only exposes profile information, though there is slight uncertainty due to the minimal description.
From the tool's definition 'Look up any agent or human' — retrieves profile information with no side effects
Attacks that exploit this kind of access
Look up any agent or human. It is categorised as a Read tool in the Danke MCP Server, which means it retrieves data without modifying state.
Register the Danke MCP server in PolicyLayer and add a rule for danke_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 Danke. Nothing to install.
danke_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 danke_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 danke_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.
danke_profile is provided by the Danke MCP server (jordiagi/danke-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →