source_events_ingest

Run source-events.ingest through the Appaloft application operation catalog. Shared with HTTP/API.

SERVERAppaloft SOURCE@appaloft/mcp

High RISK CLASS

Category Execute

Parameters 126 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/appaloft-mcp/source-events-ingest.md

WHAT IT DOES

What source_events_ingest does on Appaloft

AI agents invoke source_events_ingest to trigger actions in Appaloft. 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.

Parameter	Type	Required
`ref`	string	Yes
`forced`	boolean	—
`revision`	string	Yes
`eventKind`	string	Yes
`deliveryId`	string	—
`receivedAt`	string	—
`sourceKind`	string	Yes
`verification`	object	Yes
`refChangeKind`	string	—
`beforeRevision`	string	—
`idempotencyKey`	string	—
`sourceIdentity`	object	Yes

Parameters from the server's own tool schema.

RISK

Why source_events_ingest is rated High

source_events_ingest triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Risk signalsHigh parameter count (20 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs source_events_ingest safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For source_events_ingest, this is the rule to start with:

source_events_ingest Rate-limited

source_events_ingest stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "source_events_ingest": {
      "limits": [
        {
          "counter": "source_events_ingest_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every source_events_ingest call is checked against it from then on.

FAQ

Questions about source_events_ingest

What does the source_events_ingest tool do? +

Run source-events.ingest through the Appaloft application operation catalog. Shared with HTTP/API. It is categorised as a Execute tool in the Appaloft MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does source_events_ingest accept? +

source_events_ingest accepts 12 parameters: ref, forced, revision, eventKind, deliveryId, receivedAt, sourceKind, verification, refChangeKind, beforeRevision, idempotencyKey, sourceIdentity. Required: ref, revision, eventKind, sourceKind, verification, sourceIdentity. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on source_events_ingest? +

Register the Appaloft MCP server in PolicyLayer and add a rule for source_events_ingest: 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 Appaloft. Nothing to install.

What risk level is source_events_ingest? +

source_events_ingest is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit source_events_ingest? +

Yes. Add a rate_limit block to the source_events_ingest 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.

How do I block source_events_ingest completely? +

Set action: deny in the PolicyLayer policy for source_events_ingest. 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.

What MCP server provides source_events_ingest? +

source_events_ingest is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Appaloft, and thousands of servers like it.

This server

All 358 Appaloft tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →