[Pro] OPTIONAL - configure validation policy BEFORE running postrc_scan. Sets: which modules are active (security, monitoring, legal-claims, legal-product), whether to block on critical/high findings, CWE suppressions (known false positives), monitoring requirements, and legal review settings (Pr...
AI agents use postrc_configure 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.
This tool creates or modifies configuration data reversibly. It writes policy settings that control how validation scans operate, but the changes are not destructive—they can be reconfigured or reset.
From the tool's definition The tool configures and saves validation policy settings to post-rc/ state: 'Sets: which modules are active (security, monitoring, legal-claims, legal-product), whether to block on critical/high findings, CWE suppressions...Saved to post-rc/ state.' This…
Attacks that exploit this kind of access
[Pro] OPTIONAL - configure validation policy BEFORE running postrc_scan. Sets: which modules are active (security, monitoring, legal-claims, legal-product), whether to block on critical/high findings, CWE suppressions (known false positives), monitoring requirements, and legal review settings (Pro tier: product domain, jurisdiction, license/accessibility checks). Defaults are reasonable - only call this if the user has specific compliance or risk tolerance requirements. Saved to post-rc/ 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_configure: 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_configure 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_configure 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_configure. 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_configure 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.
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 →