Analyze a code snippet against stored project rules.
AI agents call critique_code to retrieve information from myBrAIn without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool reads/retrieves stored project rules and analyzes code against them. This is a read/query operation with no side effects — it does not modify, execute, or delete anything. It simply performs analysis and returns feedback. Severity is low as misuse would at most surface incorrect critique.
From the tool's definition Analyze a code snippet against stored project rules
Documented attack patterns abuse exactly the kind of access critique_code gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and myBrAIn, and nothing reaches the server without passing your rules. This is the rule we recommend for critique_code:
{
"version": "1",
"default": "deny",
"tools": {
"critique_code": {}
}
}critique_code is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Analyze a code snippet against stored project rules. It is categorised as a Read tool in the myBrAIn MCP Server, which means it retrieves data without modifying state.
Register the myBrAIn MCP server in PolicyLayer and add a rule for critique_code: 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 myBrAIn. Nothing to install.
critique_code 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 critique_code 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 critique_code. 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.
critique_code is provided by the myBrAIn MCP server (lilium360/mybrain). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from myBrAIn, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 myBrAIn tools catalogued and risk-classified — across an index of 43,000+ MCP servers.