AI agents call openspec_get_project_context 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 project context information from a configuration file (project.md) without creating, modifying, deleting, or executing any operations. It has no side effects and presents minimal security risk as a data retrieval function.
From the tool's definition Tool name 'get_project_context' with description 'Get project context from project.md' indicates retrieval of data with no modification. The verb 'get' and the read-only nature of querying a markdown file confirm this is a read operation.
Documented attack patterns abuse exactly the kind of access openspec_get_project_context 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_project_context:
{
"version": "1",
"default": "deny",
"tools": {
"openspec_get_project_context": {}
}
}openspec_get_project_context 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.
Get project context from project.md. 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_project_context: 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_project_context 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_project_context 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_project_context. 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_project_context 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.