Check if commit message complies with Conventional Commit format. Can check by SHA or message directly.
AI agents call gitea_compliance_check_commit to retrieve information from Gitea MCP Tool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though gitea_compliance_check_commit only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
Check if commit message complies with Conventional Commit format. Can check by SHA or message directly. It is categorised as a Read tool in the Gitea MCP Tool MCP Server, which means it retrieves data without modifying state.
Register the Gitea MCP Tool MCP server in PolicyLayer and add a rule for gitea_compliance_check_commit: 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 Gitea MCP Tool. Nothing to install.
gitea_compliance_check_commit 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 gitea_compliance_check_commit 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 gitea_compliance_check_commit. 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.
gitea_compliance_check_commit is provided by the Gitea MCP Tool MCP server (supenbysz/gitea-mcp-tool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.