Run Trailmark preanalysis on the active engine.
AI agents invoke run_preanalysis to trigger actions in Trailmark MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a preanalysis process on an active analysis engine. While analysis itself is read-like, the act of 'running' a preanalysis is an execute operation that triggers external computation with effects dependent on the repository state and engine configuration.
From the tool's definition Tool name 'run_preanalysis' combined with description 'Run Trailmark preanalysis on the active engine' indicates execution of an analysis process. The verb 'run' explicitly indicates code execution or triggering of a computational operation.
Attacks that exploit this kind of access
Run Trailmark preanalysis on the active engine. It is categorised as a Execute tool in the Trailmark MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Trailmark MCP Server MCP server in PolicyLayer and add a rule for run_preanalysis: 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 Trailmark MCP Server. Nothing to install.
run_preanalysis is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_preanalysis 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 run_preanalysis. 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.
run_preanalysis is provided by the Trailmark MCP Server MCP server (parsiya/trailmark-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 →