cdp_cache_put_by_key
Set or update a cache entry by explicit key.
This record as markdown: /tools/atharva-joshi77-cdp-mcp/cdp-cache-put-by-key.md
What cdp_cache_put_by_key does on CDP MCP Server
AI agents use cdp_cache_put_by_key to create or update resources in CDP MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CDP MCP Server environment.
Why cdp_cache_put_by_key is rated Medium
This tool modifies cached data by setting or updating entries. While cache modifications are less critical than direct data destruction, they can affect application behavior, performance, and data consistency if misused by an agent. The Write category applies because the operation is reversible (can be overwritten or deleted by other tools like cdp_cache_delete_by_key).
From the tool's definition Tool name 'cdp_cache_put_by_key' and description 'Set or update a cache entry by explicit key' indicate data modification operations. The 'put' operation creates or modifies cache entries, which is reversible through subsequent updates or deletion.
Attacks that exploit this kind of access
The rule that runs cdp_cache_put_by_key safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CDP MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cdp_cache_put_by_key, this is the rule to start with:
cdp_cache_put_by_key stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect CDP MCP Server, apply this rule, and every cdp_cache_put_by_key call is checked against it from then on.
Questions about cdp_cache_put_by_key
Set or update a cache entry by explicit key. It is categorised as a Write tool in the CDP MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CDP MCP Server MCP server in PolicyLayer and add a rule for cdp_cache_put_by_key: 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 CDP MCP Server. Nothing to install.
cdp_cache_put_by_key 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 cdp_cache_put_by_key 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 cdp_cache_put_by_key. 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.
cdp_cache_put_by_key is provided by the CDP MCP Server MCP server (atharva-joshi77/cdp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CDP MCP Server, and thousands of servers like it.
This server
Across the catalogue