List scans, optionally filtered by application.
AI agents call get_scans to retrieve information from SentinelScan Cloud MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries existing scan data without modifying, deleting, or executing any operations. It is a pure read operation with minimal risk—the only concern would be information disclosure if the data is sensitive, but that is inherent to the security testing domain and does not elevate the tool itself beyond the Read category.
From the tool's definition Tool description states 'List scans, optionally filtered by application' and tool name is 'get_scans'. The verb 'list' and 'get' are characteristic of retrieval operations with no side effects.
Attacks that exploit this kind of access
List scans, optionally filtered by application. It is categorised as a Read tool in the SentinelScan Cloud MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SentinelScan Cloud MCP Server MCP server in PolicyLayer and add a rule for get_scans: 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 SentinelScan Cloud MCP Server. Nothing to install.
get_scans 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_scans 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_scans. 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_scans is provided by the SentinelScan Cloud MCP Server MCP server (vndpal/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 →