Verify an AI agent by its DID.
AI agents call moltrust_verify to retrieve information from MolTrust MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or validates existing data (an agent's DID verification status) without creating, modifying, deleting, or executing side effects. It is a pure read operation on a trust/credential system. Severity is low because verification queries have minimal blast radius—an attacker cannot cause harm through misuse beyond obtaining information about agent identities.
From the tool's definition Tool name 'verify' and description 'Verify an AI agent by its DID' indicate a query/lookup operation that checks or retrieves verification status of an identity.
Attacks that exploit this kind of access
Verify an AI agent by its DID. It is categorised as a Read tool in the MolTrust MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MolTrust MCP Server MCP server in PolicyLayer and add a rule for moltrust_verify: 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 MolTrust MCP Server. Nothing to install.
moltrust_verify 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 moltrust_verify 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 moltrust_verify. 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.
moltrust_verify is provided by the MolTrust MCP Server MCP server (pypi:moltrust-mcp-server). 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 →