New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

accept_capacity_terms

Use this when the user has read and agreed to DC Hub's capacity introduction terms (https://dchub.cloud/listings#terms): records that acceptance, once per terms version, so Capacity Source listing details open for them. Call it when source_capacity returns a listing locked with access.reason term...

SERVERMcp Server SOURCEhttps://dchub.cloud/mcp
Low RISK CLASS
Category Read
Parameters 20 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cloud-dchub-mcp-server/accept-capacity-terms.md

What accept_capacity_terms does on Mcp Server

AI agents call accept_capacity_terms to retrieve information from Mcp Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
accept_terms boolean — Set true ONLY after your human has read and agreed to the introduction terms at https://dchub.cloud/listings#terms. Unless it is exactly true, nothing is sent
terms_version string — The terms version your human agreed to, e.g. access.unlock.terms.version from source_capacity. Omit to send the version currently published

Parameters from the server's own tool schema.

Why accept_capacity_terms is rated Low

Even though accept_capacity_terms only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about accept_capacity_terms

What does the accept_capacity_terms tool do? +

Use this when the user has read and agreed to DC Hub's capacity introduction terms (https://dchub.cloud/listings#terms): records that acceptance, once per terms version, so Capacity Source listing details open for them. Call it when source_capacity returns a listing locked with access.reason terms_acceptance_required, never on your own judgement: nothing opens without your human's agreement. Requires an identified caller (claim_free_key, then bind_email with your human's address, or an OAuth connection) and accept_terms=true. Returns accepted and the terms version, recorded in DC Hub's lead register. Do NOT use to request an introduction (use request_capacity_intro) or to browse listings (use source_capacity). It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.

What parameters does accept_capacity_terms accept? +

accept_capacity_terms accepts 2 parameters: accept_terms, terms_version. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on accept_capacity_terms? +

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

What risk level is accept_capacity_terms? +

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

Can I rate-limit accept_capacity_terms? +

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

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

accept_capacity_terms is provided by the Mcp Server MCP server (https://dchub.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Mcp Server, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mcp Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.