Medium Risk

kiwi_feedback-to-devs

[kiwi] Send feedback to the dev of the Kiwi MCP server.

Part of the MolTravel server.

kiwi_feedback-to-devs can modify MolTravel data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE MOLTRAVEL →

Free to start. No card required.

AI agents use kiwi_feedback-to-devs to create or modify resources in MolTravel. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call kiwi_feedback-to-devs repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach MolTravel.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "kiwi_feedback-to-devs": {
      "limits": [
        {
          "counter": "kiwi_feedback-to-devs_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full MolTravel policy for all 57 tools.

Get this rule live on your own MolTravel server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MOLTRAVEL →

View all 57 tools →

These attack patterns abuse exactly the kind of access kiwi_feedback-to-devs gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so kiwi_feedback-to-devs only ever does what you allow.

SECURE MOLTRAVEL →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the kiwi_feedback-to-devs tool do? +

[kiwi] Send feedback to the dev of the Kiwi MCP server.. It is categorised as a Write tool in the MolTravel MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on kiwi_feedback-to-devs? +

Register the MolTravel MCP server in PolicyLayer and add a rule for kiwi_feedback-to-devs: 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 MolTravel. Nothing to install.

What risk level is kiwi_feedback-to-devs? +

kiwi_feedback-to-devs is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit kiwi_feedback-to-devs? +

Yes. Add a rate_limit block to the kiwi_feedback-to-devs 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 kiwi_feedback-to-devs completely? +

Set action: deny in the PolicyLayer policy for kiwi_feedback-to-devs. 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 kiwi_feedback-to-devs? +

kiwi_feedback-to-devs is provided by the MolTravel MCP server (https://mcp.moltravel.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MolTravel tool call.

Deterministic rules across all 57 MolTravel tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.