Validate that required secrets exist in an environment. Useful for pre-deployment checks.
AI agents call keyway_validate to retrieve information from Keyway MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries the state of secrets in an environment (checking existence) with no side effects. It is purely informational, used for validation checks before deployment. No data is created, modified, deleted, or executed—only read and verified. This is a low-risk Read operation.
From the tool's definition Tool name 'keyway_validate' and description 'Validate that required secrets exist in an environment. Useful for pre-deployment checks' indicate a read-only operation that checks for the presence of secrets without modifying, deleting, or executing code.
Attacks that exploit this kind of access
Validate that required secrets exist in an environment. Useful for pre-deployment checks. It is categorised as a Read tool in the Keyway MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Keyway MCP Server MCP server in PolicyLayer and add a rule for keyway_validate: 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 Keyway MCP Server. Nothing to install.
keyway_validate 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 keyway_validate 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 keyway_validate. 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.
keyway_validate is provided by the Keyway MCP Server MCP server (keywaysh/keyway-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 →