Build the URL where the payer authorizes a consent at their bank. This is a helper — it does not call Iniciador. Returns the standard OFB authorization URL using the consent id + redirect URI.
AI agents call get_authorization_url to retrieve information from Mcp Ap2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and formats authorization URL information for display to a user. It does not execute transactions, modify data, delete anything, or move money. The explicit statement that it 'does not call Iniciador' confirms it has no side effects. The most severe action is returning a formatted string derived from input parameters (consent id + redirect URI), which is a Read operation.
From the tool's definition Tool description states it 'Build[s] the URL' and 'Returns the standard OFB authorization URL' — a read-only operation that constructs and returns a URL without modifying state, calling external systems, or moving funds.
Documented attack patterns abuse exactly the kind of access get_authorization_url gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for get_authorization_url:
{
"version": "1",
"default": "deny",
"tools": {
"get_authorization_url": {}
}
}get_authorization_url 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.
Build the URL where the payer authorizes a consent at their bank. This is a helper — it does not call Iniciador. Returns the standard OFB authorization URL using the consent id + redirect URI. It is categorised as a Read tool in the Mcp Ap2 MCP Server, which means it retrieves data without modifying state.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for get_authorization_url: 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 Ap2. Nothing to install.
get_authorization_url 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_authorization_url 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_authorization_url. 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_authorization_url is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, 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 Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.