Assess branch hygiene (divergence, worktree cleanliness, staleness, and target alignment) before merge/PR.
AI agents call branch_hygiene_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.
The tool performs a read-only assessment and generates a report about branch state. It reads git metadata (divergence, cleanliness, staleness, alignment) without modifying any data or triggering any operations. Blast radius is low since misuse only reveals repository state information.
From the tool's definition Assess branch hygiene (divergence, worktree cleanliness, staleness, and target alignment) — purely analytical/reporting function with no side effects
Attacks that exploit this kind of access
Assess branch hygiene (divergence, worktree cleanliness, staleness, and target alignment) before merge/PR. 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 branch_hygiene_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.
branch_hygiene_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 branch_hygiene_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 branch_hygiene_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.
branch_hygiene_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 →