Create a vendor (supplier). DisplayName is required and must be unique.
AI agents use create_vendor 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 new vendor records in an Argentine tax authority system. It is a Write operation (creates data reversibly) rather than Execute because it simply adds a structured record without executing arbitrary code or triggering complex external operations.
From the tool's definition Tool name 'create_vendor' and description 'Create a vendor (supplier)' indicates data creation. The requirement that 'DisplayName is required and must be unique' confirms this is a write operation that creates new vendor records in the AFIP invoicing system.
Documented attack patterns abuse exactly the kind of access create_vendor 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 create_vendor:
{
"version": "1",
"default": "deny",
"tools": {
"create_vendor": {
"limits": [
{
"counter": "create_vendor_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_vendor 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.
Create a vendor (supplier). DisplayName is required and must be unique. 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 create_vendor: 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.
create_vendor 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 create_vendor 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 create_vendor. 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.
create_vendor 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.