AI agents call get_audit_scan_by_url 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 'get_' prefix strongly suggests a read-only retrieval operation with no side effects. While the description is empty (reducing confidence slightly), the tool name and context within an Audit service for readiness scanning indicate this retrieves existing audit data rather than modifying, deleting, or executing operations. Confidence is moderate due to lack of explicit description.
From the tool's definition Tool name 'get_audit_scan_by_url' uses the 'get' verb, indicating a retrieval operation. No description provided. Based on naming convention and context within an audit service that performs GEO readiness checks, this appears to query audit scan results.
Attacks that exploit this kind of access
get_audit_scan_by_url. 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 get_audit_scan_by_url: 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.
get_audit_scan_by_url 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_audit_scan_by_url 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_audit_scan_by_url. 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_audit_scan_by_url 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 →