Return merged command mappings for a project
AI agents call getProjectCommands to retrieve information from Smart Shell MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns command mappings without executing them, modifying them, or causing side effects. It is a data retrieval operation. The sibling tools (executeCommand, removeProjectCommand, setProjectCommand) perform the write/execute/destructive actions; this tool only reads the current state of project command configurations.
From the tool's definition Tool name 'getProjectCommands' and description 'Return merged command mappings for a project' indicate retrieval of configuration data with no modification or execution of those commands.
Attacks that exploit this kind of access
Return merged command mappings for a project. It is categorised as a Read tool in the Smart Shell MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Smart Shell MCP Server MCP server in PolicyLayer and add a rule for getProjectCommands: 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.
getProjectCommands 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 getProjectCommands 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 getProjectCommands. 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.
getProjectCommands 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 →