Low Risk

list_humor_types

Return the closed vocabulary of humor_type tags used in the index. Useful when you want to filter or reason about candidates by humor mode rather than topic — e.g. a document about endless committees might call for tech_culture_critique, while one about feeling outdated might call for interperson...

Part of the Xkcdforthat server.

list_humor_types is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE XKCDFORTHAT →

Free to start. No card required.

AI agents call list_humor_types to retrieve information from Xkcdforthat without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though list_humor_types only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_humor_types": {}
  }
}

See the full Xkcdforthat policy for all 4 tools.

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

ENFORCE ON MY XKCDFORTHAT →

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

SECURE XKCDFORTHAT →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the list_humor_types tool do? +

Return the closed vocabulary of humor_type tags used in the index. Useful when you want to filter or reason about candidates by humor mode rather than topic — e.g. a document about endless committees might call for tech_culture_critique, while one about feeling outdated might call for interpersonal_awkwardness.. It is categorised as a Read tool in the Xkcdforthat MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_humor_types? +

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

What risk level is list_humor_types? +

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

Can I rate-limit list_humor_types? +

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

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

list_humor_types is provided by the Xkcdforthat MCP server (geertjan/xkcdforthat). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Xkcdforthat tool call.

Deterministic rules across all 4 Xkcdforthat 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.