Low Risk

request_update

Request that a provider

How to control request_update ↓

What request_update does on Football Docs

AI agents call request_update as a supporting operation in Football Docs workflows.

Low Risk

Why request_update needs a policy

The description is cut off and provides insufficient information to determine what this tool does. The name 'request_update' suggests submitting a request (possibly a Write action), but given the server context of a documentation provider for AI coding agents, it may simply flag a doc update request rather than modifying data directly. Without more detail, confidence is low.

From the tool's definition Tool description is truncated and uninformative: 'Request that a provider' — the description is incomplete, leaving the action ambiguous.

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

How to control request_update

PolicyLayer is an MCP gateway — it sits between your AI agents and Football Docs, and nothing reaches the server without passing your rules. This is the rule we recommend for request_update:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "request_update": {
      "limits": [
        {
          "counter": "request_update_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

request_update gets a rate cap, and everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Football Docs — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
SET A RULE FOR THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about request_update

What does the request_update tool do? +

Request that a provider. It is categorised as a Other tool in the Football Docs MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on request_update? +

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

What risk level is request_update? +

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

Can I rate-limit request_update? +

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

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

request_update is provided by the Football Docs MCP server (withqwerty/football-docs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Football Docs tool call.

Start from Football Docs, 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.

5 Football Docs tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.