Update profile fields on a Rapyd ewallet (user). Pass the ewallet id plus only the fields you want to change. Contact-level edits (address, identification) go through the contact endpoints — this updates user-level fields.
AI agents use update_wallet to create or update resources in Mcp Afip — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Afip environment.
This tool modifies user profile data in a wallet system reversibly—fields can be changed again if needed. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or perform read-only operations (Read). The medium severity reflects that incorrect updates could affect user account integrity or access, but changes are generally reversible through subsequent updates.
From the tool's definition Tool description states 'Update profile fields on a Rapyd ewallet (user)' and 'this updates user-level fields.' The term 'Update' and the explicit mention of modifying profile fields indicates data modification.
Documented attack patterns abuse exactly the kind of access update_wallet gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Afip, and nothing reaches the server without passing your rules. This is the rule we recommend for update_wallet:
{
"version": "1",
"default": "deny",
"tools": {
"update_wallet": {
"limits": [
{
"counter": "update_wallet_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_wallet 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.
Update profile fields on a Rapyd ewallet (user). Pass the ewallet id plus only the fields you want to change. Contact-level edits (address, identification) go through the contact endpoints — this updates user-level fields. It is categorised as a Write tool in the Mcp Afip MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Afip MCP server in PolicyLayer and add a rule for update_wallet: 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 Mcp Afip. Nothing to install.
update_wallet 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 update_wallet 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 update_wallet. 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.
update_wallet is provided by the Mcp Afip MCP server (codespar/mcp-dev-latam). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Afip, 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.
1300 Mcp Afip tools catalogued and risk-classified — across an index of 43,000+ MCP servers.