get_daily_cost_trend
AI agents call get_daily_cost_trend to retrieve information from AWS FinOps MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries historical cost trend data from AWS. There is no indication it modifies, deletes, executes code, or commits financial transactions—it fetches information for analysis. The lack of a description lowers confidence slightly, but the naming convention and sibling context strongly suggest a data retrieval function.
From the tool's definition Tool name 'get_daily_cost_trend' indicates retrieval of cost data trends without modification. Sibling tools (analyze_*, find_*) follow a Read pattern of querying and analyzing AWS resources.
Attacks that exploit this kind of access
get_daily_cost_trend. It is categorised as a Read tool in the AWS FinOps MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AWS FinOps MCP Server MCP server in PolicyLayer and add a rule for get_daily_cost_trend: 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 AWS FinOps MCP Server. Nothing to install.
get_daily_cost_trend 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_daily_cost_trend 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 get_daily_cost_trend. 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_daily_cost_trend is provided by the AWS FinOps MCP Server MCP server (prashantgupta123/aws-pillar-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →