AI agents call list_toll_sites to retrieve information from Plurity without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list' prefix strongly suggests this tool retrieves or enumerates toll sites without modifying them. While the empty description prevents higher confidence, the semantic pattern from similar tools in the same MCP server and the absence of any mutative language (create, delete, update, execute) support a Read classification.
From the tool's definition Tool name 'list_toll_sites' indicates a listing/retrieval operation. The description is empty, but the verb 'list' and the naming pattern align with sibling tools that perform read operations (e.g., 'list_intelligence_qa_pairs', 'get_toll_site',…
Attacks that exploit this kind of access
list_toll_sites. It is categorised as a Read tool in the Plurity MCP Server, which means it retrieves data without modifying state.
Register the Plurity MCP server in PolicyLayer and add a rule for list_toll_sites: 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 Plurity. Nothing to install.
list_toll_sites 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_toll_sites 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_toll_sites. 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_toll_sites is provided by the Plurity MCP server (plurity-ai/plurity-mcp). 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 →