Get filterable attributes available for an AWS service in the Pricing API. **PURPOSE:** Discover what pricing dimensions (filters) are available for a specific AWS service. **WORKFLOW:** Use this after get_pricing_service_codes() to see what filters you can apply to narrow down pricing ...
Single-target operation
Part of the AWS Pricing MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_pricing_service_attributes to retrieve information from AWS Pricing MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_pricing_service_attributes only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
get_pricing_service_attributes:
rules:
- action: allowSee the full AWS Pricing MCP Server policy for all 9 tools.
Agents calling read-class tools like get_pricing_service_attributes have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Get filterable attributes available for an AWS service in the Pricing API. **PURPOSE:** Discover what pricing dimensions (filters) are available for a specific AWS service. **WORKFLOW:** Use this after get_pricing_service_codes() to see what filters you can apply to narrow down pricing queries. **PARAMETERS:** - service_code: AWS service code from get_pricing_service_codes() (e.g., 'AmazonEC2', 'AmazonRDS') - filter (optional): Case-insensitive regex pattern to filter attribute names (e.g., "instance" matches "instanceType", "instanceFamily") **RETURNS:** List of attribute names (e.g., 'instanceType', 'location', 'storageClass') that can be used as filters. **NEXT STEPS:** - Use get_pricing_attribute_values() to see valid values for each attribute - Use these attributes in get_pricing() filters to get specific pricing data **EXAMPLE:** For 'AmazonRDS' you might get ['engineCode', 'instanceType', 'deploymentOption', 'location'].. It is categorised as a Read tool in the AWS Pricing MCP Server MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_pricing_service_attributes. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS Pricing MCP Server MCP server.
get_pricing_service_attributes 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 get_pricing_service_attributes rule in your Intercept 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 Intercept policy for get_pricing_service_attributes. 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.
get_pricing_service_attributes is provided by the AWS Pricing MCP Server MCP server (awslabs.aws-pricing-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.