List physical Stone / TON terminals for a merchant
AI agents call list_terminals 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 terminal information for read-only purposes. It queries and returns data about physical payment terminals without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal — an agent could enumerate terminals but cannot manipulate merchant infrastructure, process payments, or cause financial harm through this tool alone. It is clearly a Read operation.
From the tool's definition The tool name is 'list_terminals' and the description states it 'List[s] physical Stone / TON terminals for a merchant' — a pure retrieval operation with no modification, deletion, or execution of code/commands.
Documented attack patterns abuse exactly the kind of access list_terminals 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 list_terminals:
{
"version": "1",
"default": "deny",
"tools": {
"list_terminals": {}
}
}list_terminals 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.
List physical Stone / TON terminals for a merchant. 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 list_terminals: 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.
list_terminals 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 list_terminals 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 list_terminals. 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.
list_terminals 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.