get_issues
AI agents call get_issues 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 security issue data without modifying, deleting, or executing operations. The 'get_' prefix and context of sibling read-only tools indicate it is a simple data query operation with no side effects. Confidence is slightly reduced due to empty tool description, but naming and server context strongly indicate retrieval semantics.
From the tool's definition Tool name 'get_issues' with prefix 'get_' indicates data retrieval. Sibling tools (get_application_details, get_applications, get_dashboard_summary, get_issue_details, get_scan_details, get_scans) are all read-only query operations.
Attacks that exploit this kind of access
get_issues. 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_issues: 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_issues 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_issues 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_issues. 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_issues 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 →