AI agents call check_cloud_readiness to retrieve information from Abap without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and analyzes ABAP code to determine compliance with ABAP Cloud standards. It performs pure analysis (parsing, assessment) with no side effects, no code execution, no data modification, and no destructive operations. It is a read-only static analysis tool that returns information about code readiness without changing anything.
From the tool's definition The tool 'check_cloud_readiness' is described as assessing and parsing ABAP source code. The description indicates it performs static analysis and readiness evaluation ('Assess how far ABAP source is from ABAP Cloud') without modifying, executing, or deleting…
Attacks that exploit this kind of access
Assess how far ABAP source is from ABAP Cloud (Clean Core tier 1) by parsing it twice — once at a classic. It is categorised as a Read tool in the Abap MCP Server, which means it retrieves data without modifying state.
Register the Abap MCP server in PolicyLayer and add a rule for check_cloud_readiness: 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 Abap. Nothing to install.
check_cloud_readiness 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 check_cloud_readiness 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 check_cloud_readiness. 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.
check_cloud_readiness is provided by the Abap MCP server (abap-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 →