Veritabanına yeni görev ekler
AI agents use create-task-db to create or update resources in MCP Person Registration System — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Person Registration System environment.
This tool creates new data records (tasks) in the database, which is a reversible Write operation. It is not Destructive because task creation can be undone by deletion. Severity is medium because unauthorized task creation could pollute the database with unwanted records, but the impact is limited to one record type and reversible.
From the tool's definition Tool name 'create-task-db' and description 'Veritabanına yeni görev ekler' (adds a new task to the database) indicate data creation. The tool creates/inserts new records into a PostgreSQL database through the Express MCP server.
Attacks that exploit this kind of access
Veritabanına yeni görev ekler. It is categorised as a Write tool in the MCP Person Registration System MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Person Registration System MCP server in PolicyLayer and add a rule for create-task-db: 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 Person Registration System. Nothing to install.
create-task-db 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 create-task-db 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 create-task-db. 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.
create-task-db is provided by the MCP Person Registration System MCP server (zeyneptncr/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 →