AI agents use manage_kv_store to create or update resources in Kestra Python MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kestra Python MCP Server environment.
The tool name 'manage_kv_store' most naturally implies write operations (create, update, set) on a key-value store without explicit mention of deletion. However, 'manage' is ambiguous and could encompass destructive operations. Without a description, confidence is reduced significantly.
From the tool's definition Tool name 'manage_kv_store' suggests key-value store operations; sibling tools include destructive operations (delete_execution_logs, delete_flow_logs) and write operations (create_flow_from_yaml, execute_flow), but no description provided to clarify exact…
Documented attack patterns abuse exactly the kind of access manage_kv_store gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kestra Python MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for manage_kv_store:
{
"version": "1",
"default": "deny",
"tools": {
"manage_kv_store": {
"limits": [
{
"counter": "manage_kv_store_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}manage_kv_store 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.
Free to start. No card required.
manage_kv_store. It is categorised as a Write tool in the Kestra Python MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kestra Python MCP Server MCP server in PolicyLayer and add a rule for manage_kv_store: 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 Kestra Python MCP Server. Nothing to install.
manage_kv_store 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 manage_kv_store 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 manage_kv_store. 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.
manage_kv_store is provided by the Kestra Python MCP Server MCP server (kestra-io/mcp-server-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kestra Python MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
39 Kestra Python MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.