Generate a TypeScript client that calls Kalendis API directly with x-api-key authentication
AI agents use generate-backend-client to create or update resources in Kalendis MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kalendis MCP environment.
This tool creates new code that will be used to interact with the Kalendis API. While code generation itself is reversible (the generated code can be deleted or replaced), it modifies the codebase by adding a new authenticated client.
From the tool's definition Tool generates a TypeScript client (creates new code artifact) and establishes API authentication mechanism. Description explicitly states it 'Generate[s] a TypeScript client' which is a write/create operation.
Attacks that exploit this kind of access
Generate a TypeScript client that calls Kalendis API directly with x-api-key authentication. It is categorised as a Write tool in the Kalendis MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kalendis MCP server in PolicyLayer and add a rule for generate-backend-client: 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 Kalendis MCP. Nothing to install.
generate-backend-client is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the generate-backend-client 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.
Set action: deny in the PolicyLayer policy for generate-backend-client. 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.
generate-backend-client is provided by the Kalendis MCP server (kalendis-dev/kalendis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →