This tool help create a connector from unstructured server to destination where the data will be stored
AI agents use create_destination to create or update resources in Daraja MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Daraja MCP environment.
This tool creates (writes) a connector that directs data flow to a storage destination. While it modifies system configuration, it is reversible and does not directly execute financial transactions, delete data, or run arbitrary code.
From the tool's definition Tool description states it 'create[s] a connector...to destination where the data will be stored', indicating creation of configuration or data routing setup.
Documented attack patterns abuse exactly the kind of access create_destination gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Daraja MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create_destination:
{
"version": "1",
"default": "deny",
"tools": {
"create_destination": {
"limits": [
{
"counter": "create_destination_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_destination 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.
This tool help create a connector from unstructured server to destination where the data will be stored. It is categorised as a Write tool in the Daraja MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Daraja MCP server in PolicyLayer and add a rule for create_destination: 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 Daraja MCP. Nothing to install.
create_destination 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 create_destination 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 create_destination. 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.
create_destination is provided by the Daraja MCP server (jameskanyiri/darajamcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Daraja MCP, 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.
8 Daraja MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.