source_events_complete_check

Run source-events.complete-check through the Appaloft application operation catalog.

SERVERAppaloft SOURCE@appaloft/mcp

Medium RISK CLASS

Category Write

Parameters 76 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-complete-check.md

WHAT IT DOES

What source_events_complete_check does on Appaloft

AI agents use source_events_complete_check to create or update resources in Appaloft, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Appaloft environment.

Parameter	Type	Required
`check`	object	Yes
`revision`	string	Yes
`deliveryId`	string	Yes
`receivedAt`	string	—
`sourceKind`	string	Yes
`verification`	object	Yes
`sourceIdentity`	object	Yes

Parameters from the server's own tool schema.

RISK

Why source_events_complete_check is rated Medium

An AI agent can call source_events_complete_check faster than any human can review: one bad instruction and it creates or modifies resources in Appaloft by the hundred, each call as confident as the last.

Risk signalsHigh parameter count (17 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs source_events_complete_check 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_complete_check, this is the rule to start with:

source_events_complete_check Rate-limited

source_events_complete_check stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_complete_check": {
      "limits": [
        {
          "counter": "source_events_complete_check_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_complete_check call is checked against it from then on.

FAQ

Questions about source_events_complete_check

What does the source_events_complete_check tool do? +

Run source-events.complete-check through the Appaloft application operation catalog. It is categorised as a Write tool in the Appaloft MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does source_events_complete_check accept? +

source_events_complete_check accepts 7 parameters: check, revision, deliveryId, receivedAt, sourceKind, verification, sourceIdentity. Required: check, revision, deliveryId, 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_complete_check? +

Register the Appaloft MCP server in PolicyLayer and add a rule for source_events_complete_check: 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_complete_check? +

source_events_complete_check is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit source_events_complete_check? +

Yes. Add a rate_limit block to the source_events_complete_check 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_complete_check completely? +

Set action: deny in the PolicyLayer policy for source_events_complete_check. 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_complete_check? +

source_events_complete_check 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 428 Appaloft tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →