Create a scan configuration
AI agents use create_scan to create or update resources in Trackings MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Trackings MCP Server environment.
This tool creates scan configurations, which is a write operation that modifies state by adding new records. It is not destructive (configurations can be modified or deleted later), not execute (it configures rather than runs operations directly), and not read-only.
From the tool's definition Tool description states 'Create a scan configuration', which creates a new data record within the trackings.ai service. The tool name 'create_scan' and description language indicate reversible creation of configuration data.
Attacks that exploit this kind of access
Create a scan configuration. It is categorised as a Write tool in the Trackings MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Trackings MCP Server MCP server in PolicyLayer and add a rule for create_scan: 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 Trackings MCP Server. Nothing to install.
create_scan 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_scan 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_scan. 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_scan is provided by the Trackings MCP Server MCP server (peterw/trackings-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 →