{"version":"2.1.280","anchor":"mcp-elicitation-requests-now-rate-limited-and-size-capped","canonical_anchor":"mcp-elicitation-requests-now-rate-limited-and-size-capped","heading":"MCP elicitation requests now rate-limited and size-capped","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/mcp-elicitation-requests-now-rate-limited-and-size-capped","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### MCP elicitation requests now rate-limited and size-capped\n\nMCP elicitation requests from connected servers are now rate-limited and size-capped\n\n**What**\n\nAn MCP server (a connected tool provider that extends Claude Code) can send an 'elicitation' request, which asks the user for input mid-task. The handler that answers these requests now enforces per-connection limits:\n\n- a maximum number of outstanding elicitations at once\n\n- a maximum number admitted per minute\n\n- a maximum size for the serialized request, measured with a new size estimator\n\nRequests that exceed any of these limits are refused or cancelled instead of being processed.\n\n**Why**\n\nThis prevents a misbehaving or overly chatty MCP server from flooding you with input requests or sending oversized ones.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}