5 tools. 5 can modify or destroy data without limits.
5 write tools that can modify data. Rate limits recommended.
Last updated:
Write operations (clone_build_config, create_build_config, manage_build_steps) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Intercept sits between your agent and Teamcity. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.
npx -y @policylayer/intercept scan -- npx -y @daghis/teamcity-mcp clone_build_config:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
The Teamcity server has 5 write tools including clone_build_config, create_build_config, manage_build_steps. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.
5 tools across 1 categories: Write. 0 are read-only. 5 can modify, create, or delete data.
One line change. Instead of running the Teamcity server directly, prefix it with Intercept: intercept -c io-github-daghis-teamcity.yaml -- npx -y @@daghis/teamcity-mcp. Download a pre-built policy from policylayer.com/policies/io-github-daghis-teamcity and adjust the limits to match your use case.
Set budgets, approvals, and hard limits across MCP servers.
npx -y @policylayer/intercept init