Approve a pending JIT access request. Subject to the 4-eyes rule on the server: the approver cannot be the requester. Capturing a documented
AI agents use approve_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 access control state by approving JIT (Just-In-Time) access requests, which is a reversible write operation. While it grants sensitive permissions, it does not execute code, delete data, or move money. The high severity reflects that improper approval could grant unauthorized access to KVM Fleet devices, but the 4-eyes rule mitigates some risk.
From the tool's definition Tool name 'approve_access' and description indicating it 'Approve[s] a pending JIT access request' represents a state-changing operation that grants access permissions.
Attacks that exploit this kind of access
Approve a pending JIT access request. Subject to the 4-eyes rule on the server: the approver cannot be the requester. Capturing a documented. 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 approve_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.
approve_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 approve_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 approve_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.
approve_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 →