Open a JIT access request to a device. duration_minutes ∈ {15, 60, 240, 480}.
AI agents use request_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 creates a new access request (a Write operation), but the downstream impact is high because it initiates a privileged access workflow to a device. If misused by an AI agent, it could grant unauthorized access to sensitive infrastructure. It is reversible (requests can be denied/revoked), so it doesn't reach Destructive, but the security implications elevate severity to high.
From the tool's definition 'Open a JIT access request to a device' — creates a new Just-In-Time access request record with a specified duration
Attacks that exploit this kind of access
Open a JIT access request to a device. duration_minutes ∈ {15, 60, 240, 480}. 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 request_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.
request_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 request_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 request_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.
request_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 →