Deny a pending JIT access request. Optional reason.
AI agents use deny_access to create or update resources in KVMFleet MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your KVMFleet MCP Server environment.
This tool modifies the state of a Just-In-Time access request by denying it, which is a reversible state change (the request could potentially be re-submitted or re-approved). It does not delete data, but it does have significant security implications — denying access could block legitimate users or administrators from accessing critical infrastructure.
From the tool's definition Deny a pending JIT access request
Attacks that exploit this kind of access
Deny a pending JIT access request. Optional reason. It is categorised as a Write tool in the KVMFleet MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the KVMFleet MCP Server MCP server in PolicyLayer and add a rule for deny_access: 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 KVMFleet MCP Server. Nothing to install.
deny_access is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the deny_access 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 deny_access. 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.
deny_access is provided by the KVMFleet MCP Server MCP server (kvmfleet/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 →