AI agents use portal-mutation to create or update resources in SettleMint — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SettleMint environment.
In GraphQL, a 'mutation' is an operation that modifies data (create, update, or delete). Given the SettleMint blockchain context, this could involve modifying smart contract state or blockchain-related data. However, since the description is empty, confidence is low. The most likely category is Write, though it could be Destructive or Execute depending on the actual mutation.
From the tool's definition Tool name contains 'mutation', which in GraphQL terminology refers to an operation that creates, updates, or deletes data. The description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access portal-mutation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SettleMint, and nothing reaches the server without passing your rules. This is the rule we recommend for portal-mutation:
{
"version": "1",
"default": "deny",
"tools": {
"portal-mutation": {
"limits": [
{
"counter": "portal-mutation_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}portal-mutation stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
portal-mutation. It is categorised as a Write tool in the SettleMint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SettleMint MCP server in PolicyLayer and add a rule for portal-mutation: 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 SettleMint. Nothing to install.
portal-mutation 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 portal-mutation 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 portal-mutation. 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.
portal-mutation is provided by the SettleMint MCP server (settlemint/sdk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SettleMint, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
55 SettleMint tools catalogued and risk-classified — across an index of 43,000+ MCP servers.