get_workflow_details

THE RISK

Low Risk

Why get_workflow_details needs a policy

This tool only retrieves and queries workflow metadata without modifying, executing, or affecting any financial transactions or data. While the server as a whole handles financial operations (M-Pesa), this specific tool is purely informational, similar to a 'describe' or 'inspect' operation. The blast radius is minimal as it cannot initiate transactions or alter system state.

From the tool's definition Tool description states it 'help get a workflow details' including name, id, status, type, sources, destinations, schedule. The verb 'get' and the absence of any modification, deletion, or execution language indicate read-only retrieval.

Documented attack patterns abuse exactly the kind of access get_workflow_details gives an agent:

POLICY

How to control get_workflow_details

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 get_workflow_details:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_workflow_details": {}
  }
}

get_workflow_details is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Daraja MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Daraja MCP tools

Financial stk_push Prompts the customer to authorize a payment on their mobile device. Execute run_workflow This tool help run a workflow. Write create_destination This tool help create a connector from unstructured server to destination where the data Write create_source This tool help create a connector from data source to unstructured server where will be pr Write create_workflow create_workflow Write generate_qr_code generate_qr_code Read fetch_documents This tool will help fetch the document analyzed during the workflow execution

All 8 Daraja MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_workflow_details

What does the get_workflow_details tool do? +

This tool help get a workflow details. such as name, id, status, type, sources, destinations, schedule. It is categorised as a Read tool in the Daraja MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_workflow_details? +

Register the Daraja MCP server in PolicyLayer and add a rule for get_workflow_details: 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.

What risk level is get_workflow_details? +

get_workflow_details is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_workflow_details? +

Yes. Add a rate_limit block to the get_workflow_details 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.

How do I block get_workflow_details completely? +

Set action: deny in the PolicyLayer policy for get_workflow_details. 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.

What MCP server provides get_workflow_details? +

get_workflow_details 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.

Enforce policy on every Daraja MCP tool call.

Start from Daraja MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →