Fetch the required shipping parameters for an order before calling ship_order. Returns which of pickup / dropoff / non_integrated is expected and lists valid address_id, pickup_time_id, branch_id, slug values for the order
AI agents call get_shipping_parameter 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 queries configuration or metadata needed for a subsequent shipping operation. It retrieves and lists valid parameter values without creating, modifying, deleting, or executing any actions. The operation is purely informational — it prepares data for a later call but does not itself perform shipping or any irreversible change.
From the tool's definition Tool name is 'get_shipping_parameter' and description explicitly states it 'Fetch[es]' and 'Returns' shipping parameters — a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_shipping_parameter 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_shipping_parameter:
{
"version": "1",
"default": "deny",
"tools": {
"get_shipping_parameter": {}
}
} get_shipping_parameter 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.
Fetch the required shipping parameters for an order before calling ship_order. Returns which of pickup / dropoff / non_integrated is expected and lists valid address_id, pickup_time_id, branch_id, slug values for the order. 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_shipping_parameter: 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_shipping_parameter 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_shipping_parameter 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_shipping_parameter. 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_shipping_parameter 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.