set_custom_date_range
AI agents use set_custom_date_range to create or update resources in CX TimeFilter MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CX TimeFilter MCP Server environment.
This tool modifies dashboard time filter settings (custom date range configuration) in a reversible manner. The action is Write-class because it creates or modifies filter state that can be changed again, rather than destructively deleting data or executing arbitrary code.
From the tool's definition Tool name 'set_custom_date_range' indicates modification of dashboard filtering state; sibling tool 'set_time_period' suggests state-changing operations typical of Write category.
Attacks that exploit this kind of access
set_custom_date_range. It is categorised as a Write tool in the CX TimeFilter MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CX TimeFilter MCP Server MCP server in PolicyLayer and add a rule for set_custom_date_range: 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 CX TimeFilter MCP Server. Nothing to install.
set_custom_date_range is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_custom_date_range 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 set_custom_date_range. 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.
set_custom_date_range is provided by the CX TimeFilter MCP Server MCP server (shashi29vs/mcp). 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 →