This record as markdown: /tools/1595901624-crypto-mcp/sha384.md
What sha384 does on Crypto_MCP
AI agents call sha384 to retrieve information from Crypto_MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why sha384 is rated Low
This is a pure cryptographic hashing function. It reads input data and computes a one-way hash digest. Hash functions are deterministic, read-only operations with no side effects on stored data or external systems. The tool cannot reverse the hash, cannot modify data, and cannot trigger external operations.
From the tool's definition Tool is named 'sha384' and described as 'Calculate SHA-384 hash of a string'. SHA-384 is a cryptographic hash function that produces a fixed-size digest from input data without modification to the original data.
Attacks that exploit this kind of access
The rule that runs sha384 safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crypto_MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sha384, this is the rule to start with:
sha384 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crypto_MCP, apply this rule, and every sha384 call is checked against it from then on.
Questions about sha384
Calculate SHA-384 hash of a string. It is categorised as a Read tool in the Crypto_MCP MCP Server, which means it retrieves data without modifying state.
Register the Crypto_ MCP server in PolicyLayer and add a rule for sha384: 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 Crypto_MCP. Nothing to install.
sha384 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 sha384 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 sha384. 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.
sha384 is provided by the Crypto_ MCP server (1595901624/crypto-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crypto_, and thousands of servers like it.
This server
Across the catalogue