mt_issue_badge
AI agents use mt_issue_badge 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.
Issuing a badge creates or modifies credential data, which is a Write operation. In a trust infrastructure context involving DIDs and verifiable credentials, issuing badges could establish identity claims or reputation markers that affect downstream trust decisions.
From the tool's definition Tool name 'mt_issue_badge' contains 'issue' which indicates creation of a badge credential or credential-like object. Server context mentions 'verifiable credentials' and sibling tool 'moltguard_credential_issue' supports this interpretation.
Attacks that exploit this kind of access
mt_issue_badge. 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 mt_issue_badge: 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.
mt_issue_badge 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 mt_issue_badge 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 mt_issue_badge. 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.
mt_issue_badge 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 →