Low Risk

get_webhooks

List all webhooks for the account

How to control get_webhooks ↓

What get_webhooks does on Basecamp MCP Server

AI agents call get_webhooks to retrieve information from Basecamp MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_webhooks needs a policy

This tool retrieves webhook configuration data without modifying, deleting, or executing any operations. It is a read-only query of existing webhook settings. Exposure of webhook URLs could be sensitive, but the tool itself performs only data retrieval, which is the defining characteristic of the Read category.

From the tool's definition Tool name 'get_webhooks' and description 'List all webhooks for the account' indicate a retrieval/query operation with no side effects.

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

How to control get_webhooks

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

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

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

  1. Create a free account and register Basecamp MCP Server — 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.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_webhooks

What does the get_webhooks tool do? +

List all webhooks for the account. It is categorised as a Read tool in the Basecamp MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_webhooks? +

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

What risk level is get_webhooks? +

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

Can I rate-limit get_webhooks? +

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

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

get_webhooks is provided by the Basecamp MCP Server MCP server (qusaiisaleem/basecamp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Basecamp MCP Server tool call.

Start from Basecamp MCP Server, 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.

56 Basecamp MCP Server 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.