Force a better commit subject and provide rewrite suggestions.
AI agents use court.require_better_subject to create or update resources in Commit Conventional Message Court (CCMCP) — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Commit Conventional Message Court (CCMCP) environment.
This tool creates or modifies commit message data, which is reversible through standard git operations (amend, rebase). It does not execute arbitrary code, delete data permanently, or move money.
From the tool's definition The tool 'Force a better commit subject and provide rewrite suggestions' modifies commit messages (metadata about code changes).
Attacks that exploit this kind of access
Force a better commit subject and provide rewrite suggestions. It is categorised as a Write tool in the Commit Conventional Message Court (CCMCP) MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Commit Conventional Message Court (CCMCP) MCP server in PolicyLayer and add a rule for court.require_better_subject: 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 Commit Conventional Message Court (CCMCP). Nothing to install.
court.require_better_subject is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the court.require_better_subject 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 court.require_better_subject. 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.
court.require_better_subject is provided by the Commit Conventional Message Court (CCMCP) MCP server (jiseong-choi/ccmcp). 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 →