Aggregate Git quality checks into a single merge-readiness decision (ready, needs_attention, blocked).
AI agents call merge_readiness_report to retrieve information from MCP SAPUI5 Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and aggregates existing Git quality check results to produce a report/decision. It does not modify any data, execute code, or perform destructive operations — it is purely an analytical/reporting tool that queries state and summarizes findings.
From the tool's definition Aggregate Git quality checks into a single merge-readiness decision (ready, needs_attention, blocked)
Attacks that exploit this kind of access
Aggregate Git quality checks into a single merge-readiness decision (ready, needs_attention, blocked). It is categorised as a Read tool in the MCP SAPUI5 Server MCP Server, which means it retrieves data without modifying state.
Register the MCP SAPUI5 Server MCP server in PolicyLayer and add a rule for merge_readiness_report: 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 MCP SAPUI5 Server. Nothing to install.
merge_readiness_report 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 merge_readiness_report 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 merge_readiness_report. 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.
merge_readiness_report is provided by the MCP SAPUI5 Server MCP server (santiagosanmartinn/mcpui5server). 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 →