get_schedule_details

THE RISK

Low Risk

Why get_schedule_details needs a policy

The tool name strongly suggests a read-only operation that retrieves schedule details from an EKS context. No mutation, deletion, execution, or financial keywords are present. The empty description prevents higher confidence, but the naming convention ('get_*') is a reliable indicator of read-only behavior in AWS APIs and MCP contexts.

From the tool's definition Tool name 'get_schedule_details' indicates a retrieval operation. The verb 'get' and noun 'schedule_details' suggest querying or fetching schedule information without modification. Description is empty, which reduces certainty.

Documented attack patterns abuse exactly the kind of access get_schedule_details gives an agent:

POLICY

How to control get_schedule_details

PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon EKS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_schedule_details:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_schedule_details": {}
  }
}

get_schedule_details is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Amazon EKS MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Amazon EKS MCP Server tools

Destructive bulk_delete_by_criteria bulk_delete_by_criteria Destructive cache_delete Delete a value from the cache. Destructive cache_delete_many Delete multiple values from the cache. Destructive cache_delete_multi Delete multiple values from the cache (alias for delete_many). Destructive delete delete Destructive delete_access_key delete_access_key Destructive delete_agent_runtime delete_agent_runtime Destructive delete_agent_runtime_endpoint delete_agent_runtime_endpoint

All 805 Amazon EKS MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

Roll out MCP under one policy → Per-person scoped tokens, one central policy, and full audit across every server your team connects.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →
PolicyLayer vs alternatives → How deterministic, per-call MCP policy compares with gateways, identity layers, and authorisation platforms.

FAQ

Questions about get_schedule_details

What does the get_schedule_details tool do? +

get_schedule_details. It is categorised as a Read tool in the Amazon EKS MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_schedule_details? +

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

What risk level is get_schedule_details? +

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

Can I rate-limit get_schedule_details? +

Yes. Add a rate_limit block to the get_schedule_details 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_schedule_details completely? +

Set action: deny in the PolicyLayer policy for get_schedule_details. 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_schedule_details? +

get_schedule_details is provided by the Amazon EKS MCP Server MCP server (awslabs.eks-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Amazon EKS MCP Server tool call.

Start from Amazon EKS MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →