moltrust_register
AI agents use moltrust_register to create or update resources in MolTrust MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MolTrust MCP Server environment.
Registration typically creates or modifies identity records reversibly. Given the trust/DID/credential context, this likely creates a new agent identity or enrollment record rather than reading or executing arbitrary operations. Without a description, confidence is moderate. Categorized as Write rather than Execute because registration is a standard data-creation operation, not dynamic code execution.
From the tool's definition Tool name 'moltrust_register' suggests registration or enrollment in a trust infrastructure system; parent server context involves DIDs (Decentralized Identifiers), verifiable credentials, and USDC, implying identity or account creation.
Attacks that exploit this kind of access
moltrust_register. It is categorised as a Write tool in the MolTrust MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MolTrust MCP Server MCP server in PolicyLayer and add a rule for moltrust_register: 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_register is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the moltrust_register 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_register. 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_register 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.
moltrust_register is one line of MolTrust MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →