AI agents call openspec_get_critique_result to retrieve information from OpenSpec MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries critique results for changes in the spec management workflow. It has no side effects—it merely fetches existing review data, whether current or from history. No data is created, modified, deleted, or executed. Classification as Read is appropriate for a query/retrieval operation on workflow metadata.
From the tool's definition Tool name 'openspec_get_critique_result' combined with description 'Get critique result of a change (latest or historical records)' indicates retrieval of existing critique/review data without modification.
Documented attack patterns abuse exactly the kind of access openspec_get_critique_result gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenSpec MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for openspec_get_critique_result:
{
"version": "1",
"default": "deny",
"tools": {
"openspec_get_critique_result": {}
}
} openspec_get_critique_result 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.
获取变更的评审结果(最新或历史记录). It is categorised as a Read tool in the OpenSpec MCP MCP Server, which means it retrieves data without modifying state.
Register the OpenSpec MCP server in PolicyLayer and add a rule for openspec_get_critique_result: 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 OpenSpec MCP. Nothing to install.
openspec_get_critique_result 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 openspec_get_critique_result 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 openspec_get_critique_result. 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.
openspec_get_critique_result is provided by the OpenSpec MCP server (lumiaqian/openspec-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OpenSpec MCP, 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.
40 OpenSpec MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.