[Pro] Generate a formal validation report from scan results. Call after postrc_scan to produce a shareable markdown document with: findings summary, severity breakdown, override records, and remediation recommendations. Useful for stakeholders, compliance, or audit trails. Saved to post-rc/. Read...
AI agents use postrc_report to create or update resources in RC Engine — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RC Engine environment.
Despite being described as 'Read-only - does not modify scan state', the tool explicitly saves a generated markdown document to the post-rc/ directory. Writing a new file to disk is a Write operation. It does not modify existing scan data, but it does create a new artifact, placing it in the Write category.
From the tool's definition 'Generate a formal validation report', 'Saved to post-rc/'
Attacks that exploit this kind of access
[Pro] Generate a formal validation report from scan results. Call after postrc_scan to produce a shareable markdown document with: findings summary, severity breakdown, override records, and remediation recommendations. Useful for stakeholders, compliance, or audit trails. Saved to post-rc/. Read-only - does not modify scan state. It is categorised as a Write tool in the RC Engine MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RC Engine MCP server in PolicyLayer and add a rule for postrc_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 RC Engine. Nothing to install.
postrc_report 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 postrc_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 postrc_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.
postrc_report is provided by the RC Engine MCP server (originalrashmi/rc-engine-product-framework). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
postrc_report is one line of RC Engine's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →