which_command

A read tool on the Allcanuse MCP server.

SERVERAllcanuse SOURCEra1nyxin/allcanuse-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ra1nyxin-allcanuse-mcp/which-command.md

WHAT IT DOES

What which_command does on Allcanuse

AI agents call which_command to retrieve information from Allcanuse without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why which_command is rated Low

The Unix/Windows 'which' command locates executables in PATH and returns their location. It is a read-only lookup operation with no side effects. Confidence is reduced due to the empty description, but the well-known semantics of 'which' strongly suggest a read operation.

From the tool's definition Tool name 'which_command' — description is empty/uninformative

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs which_command safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Allcanuse, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For which_command, this is the rule to start with:

which_command Allowed

which_command is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "which_command": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Allcanuse, apply this rule, and every which_command call is checked against it from then on.

FAQ

Questions about which_command

What does the which_command tool do? +

which_command is a read tool on the Allcanuse MCP server. It is categorised as a Read tool in the Allcanuse MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on which_command? +

Register the Allcanuse MCP server in PolicyLayer and add a rule for which_command: 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 Allcanuse. Nothing to install.

What risk level is which_command? +

which_command is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit which_command? +

Yes. Add a rate_limit block to the which_command 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.

How do I block which_command completely? +

Set action: deny in the PolicyLayer policy for which_command. 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.

What MCP server provides which_command? +

which_command is provided by the Allcanuse MCP server (ra1nyxin/allcanuse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Allcanuse, and thousands of servers like it.

This server

All 130 Allcanuse tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →