Check if field exists in hash. Args: key: The name of the key field: The field name Returns: Boolean result or error message
AI agents call hash_exists to retrieve information from AWS without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple existence check on a hash field, which is a read-only operation with no side effects. It queries state but does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal—an agent could only learn whether a field exists in a hash structure.
From the tool's definition Tool description states 'Check if field exists in hash' with return type 'Boolean result or error message'. This is a query operation that retrieves existence information without modifying data.
Documented attack patterns abuse exactly the kind of access hash_exists gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS, and nothing reaches the server without passing your rules. This is the rule we recommend for hash_exists:
{
"version": "1",
"default": "deny",
"tools": {
"hash_exists": {}
}
}hash_exists is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check if field exists in hash. Args: key: The name of the key field: The field name Returns: Boolean result or error message. It is categorised as a Read tool in the AWS MCP Server, which means it retrieves data without modifying state.
Register the AWS MCP server in PolicyLayer and add a rule for hash_exists: 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 AWS. Nothing to install.
hash_exists 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 hash_exists 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 hash_exists. 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.
hash_exists is provided by the AWS MCP server (@awslabs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
300 AWS tools catalogued and risk-classified — across an index of 43,000+ MCP servers.