Manage MolTrust credits: check balance, view pricing, transfer credits, or view transaction history. Args: action: One of "balance", "pricing", "transfer", or "transactions" did: Agent DID (required for "balance" and "transactions") to_did: Recipient DID (required for...
Part of the MolTrust MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use moltrust_credits to create or modify resources in MolTrust. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call moltrust_credits repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach MolTrust.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
moltrust_credits:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full MolTrust policy for all 11 tools.
Agents calling write-class tools like moltrust_credits have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Manage MolTrust credits: check balance, view pricing, transfer credits, or view transaction history. Args: action: One of "balance", "pricing", "transfer", or "transactions" did: Agent DID (required for "balance" and "transactions") to_did: Recipient DID (required for "transfer") amount: Number of credits to transfer (required for "transfer", must be >= 1) reference: Optional reference string for transfers limit: Max transactions to return (default 20, for "transactions") offset: Pagination offset (default 0, for "transactions") . It is categorised as a Write tool in the MolTrust MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for moltrust_credits. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the MolTrust MCP server.
moltrust_credits 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_credits rule in your Intercept 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 Intercept policy for moltrust_credits. 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_credits is provided by the MolTrust MCP server (moltrust/moltrust-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept