ListPullThroughCacheRules
AI agents call ListPullThroughCacheRules to retrieve information from Amazon SageMaker AI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'List' prefix conventionally indicates a read-only operation that retrieves and enumerates existing resources without modification, deletion, or execution of code. Although the description is empty, the naming pattern strongly suggests this queries cache rule configurations. This carries minimal blast radius as it only exposes informational data about cache infrastructure.
From the tool's definition Tool name 'ListPullThroughCacheRules' indicates a listing/query operation that retrieves pull-through cache rules from Amazon SageMaker.
Attacks that exploit this kind of access
ListPullThroughCacheRules. It is categorised as a Read tool in the Amazon SageMaker AI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Amazon SageMaker AI MCP Server MCP server in PolicyLayer and add a rule for ListPullThroughCacheRules: 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 SageMaker AI MCP Server. Nothing to install.
ListPullThroughCacheRules is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ListPullThroughCacheRules 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 ListPullThroughCacheRules. 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.
ListPullThroughCacheRules is provided by the Amazon SageMaker AI MCP Server MCP server (awslabs.sagemaker-ai-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.