list-custom-line-items
AI agents call list-custom-line-items to retrieve information from Awslabs Valkey without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name strongly suggests a Read operation that lists/retrieves custom line items. The empty description reduces confidence slightly, but the 'list-' prefix is a standard naming convention for retrieval operations. No evidence of modification, deletion, or external execution. Classified as Read with low severity due to minimal blast radius of querying data.
From the tool's definition Tool name 'list-custom-line-items' follows the 'list-*' pattern, which conventionally retrieves or queries data without side effects.
Attacks that exploit this kind of access
list-custom-line-items. It is categorised as a Read tool in the Awslabs Valkey MCP Server, which means it retrieves data without modifying state.
Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for list-custom-line-items: 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 Awslabs Valkey. Nothing to install.
list-custom-line-items 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 list-custom-line-items 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 list-custom-line-items. 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.
list-custom-line-items is provided by the Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.