AI agents use project_context_set to create or update resources in Lockstep — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lockstep environment.
This tool creates or modifies project configuration data reversibly. While it affects shared project state used by multiple agents, the data stored is contextual metadata rather than core application data or destructive operations. Misuse could confuse coordinating agents or derail project planning, but changes are not irreversible and don't execute code or affect financial systems.
From the tool's definition Tool description explicitly states 'Store project context' which involves creating or modifying project metadata (description, goals, tech stack, acceptance criteria, tests, implementation plan).
Attacks that exploit this kind of access
Store project context (description, goals, tech stack, acceptance criteria, tests, implementation plan). Called by planner to define what the project is about. It is categorised as a Write tool in the Lockstep MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lockstep MCP server in PolicyLayer and add a rule for project_context_set: 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 Lockstep. Nothing to install.
project_context_set 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 project_context_set 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 project_context_set. 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.
project_context_set is provided by the Lockstep MCP server (tmmoore286/lockstep-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
project_context_set is one line of Lockstep'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 →