AI agents call list_intelligence_sources 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 tool name follows a standard 'list_' prefix pattern which implies retrieving or enumerating a collection of intelligence sources. No description is available, which lowers confidence slightly, but the naming convention is consistent with Read operations. The blast radius of misuse is low since this appears to be a data retrieval action with no ability to modify, delete, or execute operations.
From the tool's definition Tool name 'list_intelligence_sources' indicates a listing/retrieval operation, typical of Read category tools that query data without side effects.
Attacks that exploit this kind of access
list_intelligence_sources. 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_intelligence_sources: 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_intelligence_sources 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_intelligence_sources 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_intelligence_sources. 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_intelligence_sources 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 →