Medium Risk

create_request_record

Create a request through the experimental write API. Requires WDTK_API_KEY in the server environment.

Risk signalsAccepts raw HTML/template content (body)

Part of the What Do They Know? server.

create_request_record can modify What Do They Know? data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE WHAT DO THEY KNOW? →

Free to start. No card required.

AI agents use create_request_record to create or modify resources in What Do They Know?. 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 create_request_record 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 What Do They Know?.

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_request_record": {
      "limits": [
        {
          "counter": "create_request_record_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full What Do They Know? policy for all 8 tools.

Get this rule live on your own What Do They Know? server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY WHAT DO THEY KNOW? →

These attack patterns abuse exactly the kind of access create_request_record 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 create_request_record only ever does what you allow.

SECURE WHAT DO THEY KNOW? →

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

What does the create_request_record tool do? +

Create a request through the experimental write API. Requires WDTK_API_KEY in the server environment.. It is categorised as a Write tool in the What Do They Know? MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_request_record? +

Register the What Do They Know? MCP server in PolicyLayer and add a rule for create_request_record: 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 What Do They Know?. Nothing to install.

What risk level is create_request_record? +

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

Can I rate-limit create_request_record? +

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

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

create_request_record is provided by the What Do They Know? MCP server (bouch/whatdotheyknow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every What Do They Know? tool call.

Deterministic rules across all 8 What Do They Know? 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.