AI agents use tap_create_developer to create or update resources in Tds — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tds environment.
This tool creates a new developer entity/account on the TapTap platform, which is a reversible write operation. It modifies platform state by adding a new record, but the action is not destructive (can be undone via account deletion/removal) and does not involve financial transactions or code execution.
From the tool's definition Tool name 'tap_create_developer' and description 'user wants to create a new developer on TapTap platform' indicate data creation/modification on a platform.
Attacks that exploit this kind of access
user wants to create a new developer on TapTap platform. It is categorised as a Write tool in the Tds MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tds MCP server in PolicyLayer and add a rule for tap_create_developer: 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 Tds. Nothing to install.
tap_create_developer 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 tap_create_developer 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 tap_create_developer. 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.
tap_create_developer is provided by the Tds MCP server (@taptap/tds-mcp-server). 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 →