Get counterparties list filtered by property (Sender/Recipient/ThirdPerson) via Counterparty/getCounterparties (doc 1.6). Docs require an API key, recommend caching the directory daily, and note each page tops out at 500 rows so always filter with CounterpartyProperty/FindByString.
AI agents call counterparty_get_counterparties to retrieve information from Novaposhta without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and filters counterparty information from a directory without creating, modifying, deleting, or executing external operations. It is a standard data retrieval operation with no side effects. The severity is low because misuse would only expose existing counterparty data without enabling destructive, financial, or execution-based harm.
From the tool's definition Tool description states 'Get counterparties list filtered by property' and mentions 'getCounterparties' API endpoint. The operation retrieves data with filtering capabilities (by Sender/Recipient/ThirdPerson property) without modification or deletion.
Attacks that exploit this kind of access
Get counterparties list filtered by property (Sender/Recipient/ThirdPerson) via Counterparty/getCounterparties (doc 1.6). Docs require an API key, recommend caching the directory daily, and note each page tops out at 500 rows so always filter with CounterpartyProperty/FindByString. It is categorised as a Read tool in the Novaposhta MCP Server, which means it retrieves data without modifying state.
Register the Novaposhta MCP server in PolicyLayer and add a rule for counterparty_get_counterparties: 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 Novaposhta. Nothing to install.
counterparty_get_counterparties 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 counterparty_get_counterparties 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 counterparty_get_counterparties. 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.
counterparty_get_counterparties is provided by the Novaposhta MCP server (@shopana/novaposhta-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →