mt_shopping_issue_vc
AI agents use mt_shopping_issue_vc 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 verifiable credential creates a new, cryptographically-signed record that can be presented as proof of claims or attributes. This is a Write operation because it creates data reversibly (credentials can be revoked). It is not Execute because it does not run arbitrary code or external operations.
From the tool's definition Tool name contains 'issue_vc' (verifiable credential), and sibling tool 'moltguard_credential_issue' confirms this server issues credentials. The action of issuing a credential creates a new digital artifact.
Attacks that exploit this kind of access
mt_shopping_issue_vc. 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_shopping_issue_vc: 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_shopping_issue_vc 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_shopping_issue_vc 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_shopping_issue_vc. 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_shopping_issue_vc 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 →