Get chatbot flow/builder configuration
AI agents call get_chatbot_flow to retrieve information from Mcp Afip without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves chatbot configuration/workflow settings. The 'Get' verb and lack of any mutation language ('create', 'update', 'delete') indicates a read-only operation. Within an AFIP (Argentine tax authority) context, retrieving chatbot configuration poses minimal risk—it accesses internal system metadata rather than financial data or tax records. No side effects or irreversible actions are possible.
From the tool's definition Tool name 'get_chatbot_flow' and description 'Get chatbot flow/builder configuration' indicate retrieval of configuration data with no modification.
Documented attack patterns abuse exactly the kind of access get_chatbot_flow 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 get_chatbot_flow:
{
"version": "1",
"default": "deny",
"tools": {
"get_chatbot_flow": {}
}
} get_chatbot_flow is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get chatbot flow/builder configuration. It is categorised as a Read tool in the Mcp Afip MCP Server, which means it retrieves data without modifying state.
Register the Mcp Afip MCP server in PolicyLayer and add a rule for get_chatbot_flow: 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.
get_chatbot_flow is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_chatbot_flow 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 get_chatbot_flow. 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.
get_chatbot_flow 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.