Agents and rules
Give your agent the project rules.
Project rules put your standard into the files coding agents read. MCP lets an agent inspect findings, resolved configuration and supported fixes while it works.
{
"minHealthScore": 75,
"complexityThreshold": 10,
"gateMaxSecuritySmells": 0
}The agent can ask for the actual project context.
iris_check- Findings with rule ids and lines
iris_config- The project's resolved limits
iris_fix_safe- Preview, then apply, safe fixes
What it does
Instructions before the edit. Findings after it.
Project rules turn the repository's configuration into instructions in files coding agents read, including AGENTS.md and CLAUDE.md. They describe the project's limits, naming conventions and gate rules without asking a model to invent them.
MCP gives a connected agent tools to read the resolved configuration, inspect findings and preview supported fixes. Instructions explain the standard; analysis checks the resulting code. Neither depends on guessing whether a person or an agent wrote it.
- Write the project's rules to AGENTS.md, CLAUDE.md and supported agent instruction files.
- Inspect findings with rule identifiers and source locations through MCP.
- Preview supported safe fixes and inspect a reason when a fix is refused.
Why use it
Make the standard available when the agent needs it.
A general request to write clean code leaves the project's actual limits unstated. Rules and tools make those expectations concrete.
- Replace vague instructions with project rules
- Generate instructions from .irisconfig.json so the agent can read the same limits used by the editor, hook and CI.
- Give corrections a specific target
- MCP findings include rule identifiers, locations and severity. An agent can work from a named finding rather than an unexplained score.
- Keep automated edits bounded
- Supported safe fixes preview the exact change before application. Findings that cannot be safely fixed receive a refusal with a reason, leaving the decision visible.
How to use it
Give your agent the rules, then check its work.
Project rules and single-file core tools are Free. The MCP guide covers the setup for each supported client.
Generate the project's instructions
Run the rules command from the project with its .irisconfig.json. Review the generated instructions before using them with your agent; the default target is AGENTS.md.
From your project directory iris rulesResultYour project's configured limits are available in an agent instruction file.
Connect your agent's MCP client
Follow the client-specific setup in the MCP guide. JetBrains users should use Tools → Iris Code → Set Up MCP Server to copy the project-specific configuration.
ResultThe agent can request Iris Code tools for the project, subject to repository and team policy.
Ask for configuration and findings
Have the agent read iris_config, then use iris_check on the supported file it is changing. Single-file findings are Free. Fresh folder and workspace inspection can use signed-in Free project actions where enabled; opening owned evidence does not spend another action.
ResultThe agent receives the resolved standard and specific findings to inspect.
Review the proposed fix and recheck
Use iris_fix_safe to preview supported changes and read refusals. Review the diff and check the file again. Pro's iris_gate can also report whether the configured gate would pass.
ResultYou can assess the resulting code and evidence before accepting the change.
The capabilities, in detail.
- Agent policyFree / Pro scopes
- Decide whether coding agents may use Iris Code through its MCP server. A repository turns it off for everyone with "agentHandoff": false on any plan; Team owners and admins set it for members' machines, the team's projects, or one project. The package guard keeps answering either way.
Choose your scope
What's included.
- Free
- Project rules and core MCP tools at single-file scope are Free, including package checks before install.
- Pro and Teams
- Project inspection, dependency refreshes and new multi-file plans use applicable project access. Paid automation stays separate; owned evidence remains readable.
Know the boundary
What it doesn't promise.
Iris Code does not identify who wrote the code. It checks the result. Agent access can be disabled by repository or team policy.
Start here.
Follow the MCP setup guide, then generate project rules for the coding agents you use.