Add or update a project-specific command override
AI agents use setProjectCommand to create or update resources in Smart Shell MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Smart Shell MCP Server environment.
This tool creates or modifies command mappings that directly influence what 'executeCommand' will run. While the write operation itself is reversible (can be overridden again or removed via 'removeProjectCommand'), the consequence is severe: poisoning the command execution environment to run arbitrary or malicious commands.
From the tool's definition Tool description states 'Add or update a project-specific command override', explicitly indicating data modification.
Attacks that exploit this kind of access
Add or update a project-specific command override. It is categorised as a Write tool in the Smart Shell MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Smart Shell MCP Server MCP server in PolicyLayer and add a rule for setProjectCommand: 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 Smart Shell MCP Server. Nothing to install.
setProjectCommand 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 setProjectCommand 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 setProjectCommand. 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.
setProjectCommand is provided by the Smart Shell MCP Server MCP server (mr-wolf-gb/smart-shell-mcp). 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 →