get_time_machine_access

List all Nutanix clusters that have access to a specific Time Machine, alongside their SLA policies.

Server NDB MCP Server rouxton/ndb-mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_time_machine_access does on NDB MCP Server

AI agents call get_time_machine_access to retrieve information from NDB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_time_machine_access needs a policy

This tool performs a simple data retrieval operation to enumerate clusters and their associated Time Machine access policies. There are no side effects, no data modification, no execution of external operations, and no financial transactions. The information retrieved could be useful for understanding system configuration, but disclosure of this metadata poses minimal risk to the infrastructure.

From the tool's definition The tool description explicitly states it 'List[s] all Nutanix clusters' with 'SLA policies'—a read-only operation that retrieves and queries data without modification, creation, or deletion.

Questions about get_time_machine_access

What does the get_time_machine_access tool do? +

List all Nutanix clusters that have access to a specific Time Machine, alongside their SLA policies. It is categorised as a Read tool in the NDB MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_time_machine_access? +

Register the NDB MCP Server MCP server in PolicyLayer and add a rule for get_time_machine_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 NDB MCP Server. Nothing to install.

What risk level is get_time_machine_access? +

get_time_machine_access is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_time_machine_access? +

Yes. Add a rate_limit block to the get_time_machine_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.

How do I block get_time_machine_access completely? +

Set action: deny in the PolicyLayer policy for get_time_machine_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.

What MCP server provides get_time_machine_access? +

get_time_machine_access is provided by the NDB MCP Server MCP server (rouxton/ndb-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.