Set a bot resource value (used as bot variables / state via /resources bucket)
AI agents use set_bot_resource 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 creates or modifies bot state variables and resource values, which is reversible (can be overwritten or reset). It does not execute code, delete data, move money, or trigger external operations with uncontrolled side effects. The 'set' operation is characteristic of Write-category tools.
From the tool's definition Tool name 'set_bot_resource' combined with description 'Set a bot resource value (used as bot variables / state via /resources bucket)' indicates modification of state/variables.
Documented attack patterns abuse exactly the kind of access set_bot_resource 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 set_bot_resource:
{
"version": "1",
"default": "deny",
"tools": {
"set_bot_resource": {
"limits": [
{
"counter": "set_bot_resource_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} set_bot_resource 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.
Set a bot resource value (used as bot variables / state via /resources bucket). 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 set_bot_resource: 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.
set_bot_resource 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 set_bot_resource 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 set_bot_resource. 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.
set_bot_resource 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.