MCP Connector Policy Linter v2

Inspect mcp connector policy linter v2 workflows and return policy decisions, risk flags, cost notes, trace evidence, and recommended actions.

What this Actor does

What it does

• Processes configured public sources or user-provided records for focused mcp connector policy linter v2 monitoring.
• Emits structured rows with source references, stable identifiers, confidence, warnings, and run summary fields.
• Supports sample-mode runs so Apify Store QA and first-time users can inspect output without depending on live third-party availability.

What it does not do

• Does not scrape private, login-only, paywalled, or access-restricted data unless the user provides approved credentials for a source they control.
• Does not guarantee every field is available from every source; missing or blocked fields are returned as warnings or nulls.
• Does not make legal, financial, compliance, procurement, medical, safety, or regulatory decisions.

Who this is for

AI operations, security, governance, platform, and automation teams use this actor when they need focused mcp connector policy linter v2 output instead of a broad generic scraper or manual checking.

Buyer outcomes

• Inspect mcp connector policy linter v2 behavior before it creates avoidable cost, safety, or trust issues.
• Prioritize review with policy decisions, risk levels, budget impact, trace evidence, and recommended actions.
• Route blocked, approved, or review-required events into audit logs and operational workflows.

Data sources

Sources monitored

user-provided agent traces, tool-call records, policies, MCP manifests, actor metadata, or workflow evidence

Input

• sourceMode: use sample for a safe smoke run, or configured modes for trace/tool-call inputs.
• startUrls: optional public actor, policy, MCP manifest, or evidence URLs when the workflow uses URL-backed review.
• sourceIds: approved policy, dataset, manifest, or trace source identifiers.
• maxItems: bounded number of decisions, findings, or reports to emit.
• watchlistTerms: policy names, tools, vendors, domains, or risk terms to prioritize.
• webhookUrl: optional destination for review-required decisions or audit reports.
• outputMode: use sample records for Store validation or production output for normal runs.

How it transforms the input

• Input: agent trace, tool-call request, MCP manifest, actor metadata, policy rule, or run evidence.
• Transformation: apply policy, risk, budget, permission, side-effect, or audit checks.
• Output: allow/block/review decisions, matched policy, risk score, budget impact, reason, and recommended next action.

Output

The actor returns structured AgentOps records for tool-call decisions, policy results, budget/cost signals, prompt-injection review, repair diagnosis, trace evidence, or audit reports.

Family-specific fields to expect:

• agentGoal: What the agent or workflow was trying to accomplish.

• toolCall: Requested tool name, arguments, and execution context.

• policyDecision: Allow, block, review, or escalation decision.

• riskLevel: Risk level assigned to the action or workflow.

• budgetImpact: Estimated or observed cost impact.

• sideEffectRisk: Potential external, write, payment, or account side-effect risk.

• recommendedAction: Operational next step for the reviewer or automation.

• auditEvidence: Trace, policy, manifest, or run evidence used in the decision.

• recordId: Stable record ID for exports, dedupe, and downstream joins.

• title: Human-readable record title for review and export.

• sourceName: Source identifier used to trace where the record came from.

• sourceUrl: Direct source URL for review and audit.

• dedupeKey: Stable key used for delta mode and duplicate suppression.

• retrievedAt: Timestamp showing when the actor retrieved or generated this record.

• score: Normalized field for filtering, routing, or downstream review.

• scoreReasons: Buyer-readable explanation for the score or match.

• confidence: Normalized field for filtering, routing, or downstream review.

• errors: Normalized field for filtering, routing, or downstream review.

• runSummary: Run-level summary for counts, filters, charges, and next actions.

Pricing

This actor uses Apify pay-per-event pricing. Current public listing guidance: $29-$49 / 1,000 launch validation records until public data proof is complete. Charges are tied to buyer-visible value events such as attachment-evidence, dataset-processed, record-saved, enriched-record. Small validation runs are supported so you can inspect output before scaling a schedule.

• attachment-evidence: Charge when MCP Connector Policy Linter v2 produces Apify actor run or buyer-defined paid event. Typical price: $0.043. A run that produces 10 matching records charges only for the matched buyer-value events and remains capped by the run limit.
• dataset-processed: Base charge when MCP Connector Policy Linter v2 writes a non-empty default dataset. Typical price: $0.011. A run that produces 10 matching records charges only for the matched buyer-value events and remains capped by the run limit.
• record-saved: Charge for each buyer-visible result saved by MCP Connector Policy Linter v2. Typical price: $0.003. A run that produces 10 matching records charges only for the matched buyer-value events and remains capped by the run limit.
• enriched-record: Charge when MCP Connector Policy Linter v2 adds match scoring, source evidence, or enrichment to a saved result. Typical price: $0.022. A run that produces 10 matching records charges only for the matched buyer-value events and remains capped by the run limit.
• first-run-cap: Recommended first run budget cap. Typical price: $3.820. Start with the default small run, inspect the dataset, then raise maxItems or schedule recurring runs.

API example

curl -X POST "https://api.apify.com/v2/actors/zentrafoundry~mcp-connector-policy-linter-v2/runs" \
+  -H "Authorization: Bearer $APIFY_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{"maxItems":10,"sourceIds":[],"includeSourceUrls":true,"includeMatchReasons":true,"outputMode":"buyer-ready-records"}'

Demo run

Recommended first run

{
    "maxItems": 10,
    "sourceIds": [],
    "includeSourceUrls": true,
    "includeMatchReasons": true,
    "outputMode": "buyer-ready-records"
}

Sample output

Sample status: sample_unavailable at https://zentra.nimblique.studio/external/actor-review/samples/mcp-connector-policy-linter-v2.json. No fake sample is published; run a bounded real sample refresh before using examples in promotion.

Recommended public tasks

[
    {
        "name": "Review 10 agent/tool decisions",
        "description": "Low-cost validation run for checking policy, risk, cost, and action fields.",
        "input": {
            "maxItems": 10,
            "sourceIds": [],
            "includeSourceUrls": true,
            "includeMatchReasons": true,
            "outputMode": "buyer-ready-records",
            "actorSlug": "mcp-connector-policy-linter-v2"
        }
    },
    {
        "name": "Daily AgentOps decision review",
        "description": "Recurring review batch for tool-call risk, cost guardrails, and audit evidence.",
        "schedule": "Daily during local business hours",
        "input": {
            "maxItems": 25,
            "sourceIds": [],
            "includeSourceUrls": true,
            "includeMatchReasons": true,
            "outputMode": "buyer-ready-records",
            "actorSlug": "mcp-connector-policy-linter-v2"
        }
    }
]

Example use cases

• Review mcp connector policy linter v2 decisions before high-risk tool calls execute.
• Route policy violations, cost guardrails, and prompt-injection findings into audit logs or review queues.
• Compare agent runs by risk, confidence, budget impact, and recommended next action.
• Create customer-facing evidence for safer AI-agent operations.

Trust and compliance

• Uses user-provided agent traces, tool-call records, policies, MCP manifests, actor metadata, or workflow evidence.
• Keeps source URLs and source identifiers in output records for auditability.
• Does not require private credentials unless a source is explicitly configured for approved authenticated access.
• AgentOps outputs should be logged and reviewed before enforcing high-impact production decisions.

Reliability and QA

• Prefilled Apify Store QA input runs in sample mode and should finish within the automated quality window.
• Empty input is handled with deterministic sample or diagnostic output instead of a crash.
• Demo/sample runs suppress buyer-value charges while still writing representative dataset rows.
• Production runs use bounded maxItems, source references, warnings, and run summaries so blocked or changed targets are visible.

Limitations

• Results depend on public-source availability, source uptime, and source update cadence.
• Public sources can revise records after publication; rerun scheduled tasks for fresh evidence.
• Scores and match reasons are decision-support signals, not legal, financial, procurement, medical, safety, or regulatory advice.
• Large production runs can cost more than the default smoke run; start small, inspect output, then scale schedules.

Legal and responsible use

Use this Actor only for public data or data you are authorized to process. You are responsible for complying with applicable laws, marketplace terms, robots policies, privacy rules, and source-specific limits.

Support

Open an issue on the Actor page with the run ID, input summary, expected result, and observed result. Do not include secrets, cookies, auth headers, or private account data.

FAQ

Can I run this without URLs? Yes. The default sample mode is designed to succeed without user-supplied URLs, and URL-backed runs can use startUrls when needed.

Can I schedule it? Yes. Use sinceLastRun, watchlistTerms, and optional webhookUrl to turn the actor into a recurring alert or report workflow.

How do I verify value before scaling? Run the recommended first-run input, review the sample output fields, then increase maxItems or schedule recurring runs after the dataset matches your use case.