Get the current per-user transaction limits granted by Transak based on the user
AI agents call get_user_limits 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 queries transaction limit data for a user without modifying, executing, or deleting anything. While it relates to financial context (transaction limits on a payment protocol), it performs no financial movement or obligation. The blast radius of misuse is low—an attacker would only gain visibility into existing limit thresholds, not ability to modify limits or move funds.
From the tool's definition Tool name 'get_user_limits' and description 'Get the current per-user transaction limits' indicate a retrieval operation with no side effects. The verb 'Get' and absence of any modification, execution, or deletion language confirm this is a read-only query.
Documented attack patterns abuse exactly the kind of access get_user_limits 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_user_limits:
{
"version": "1",
"default": "deny",
"tools": {
"get_user_limits": {}
}
} get_user_limits 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 the current per-user transaction limits granted by Transak based on the user. 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_user_limits: 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_user_limits 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_user_limits 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_user_limits. 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_user_limits 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.