High Risk →

hash_new

Create hash with any available algorithm

Part of the Mcp Hashlib MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

mcp-hashlib Execute Risk 3/5

AI agents invoke hash_new to trigger processes or run actions in Mcp Hashlib. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

hash_new can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

io-github-daedalus-mcp-hashlib.yaml
tools:
  hash_new:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Mcp Hashlib policy for all 22 tools.

Tool Name hash_new
Category Execute
Risk Level High

View all 22 tools →

Agents calling execute-class tools like hash_new have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

hash_new is one of the high-risk operations in Mcp Hashlib. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the hash_new tool do? +

Create hash with any available algorithm. It is categorised as a Execute tool in the Mcp Hashlib MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on hash_new? +

Add a rule in your Intercept YAML policy under the tools section for hash_new. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Hashlib MCP server.

What risk level is hash_new? +

hash_new is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit hash_new? +

Yes. Add a rate_limit block to the hash_new rule in your Intercept 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 hash_new completely? +

Set action: deny in the Intercept policy for hash_new. 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 hash_new? +

hash_new is provided by the Mcp Hashlib MCP server (mcp-hashlib). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Mcp Hashlib

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.