list_integration_activity
Read recent integration webhook and sync activity, newest first. This is the log to check when an integration reports connected but contacts or events are not appearing: each row carries the action, status, event type, matched contact, and error. Payloads are sanitized at write time, so no creden...
This record as markdown: /tools/io-github-polnikale-sequenzy-mcp/list-integration-activity.md
What list_integration_activity does on Sequenzy Mcp
AI agents call list_integration_activity to retrieve information from Sequenzy Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_integration_activity is rated Low
This tool retrieves and queries historical integration activity logs for diagnostic purposes. It has no side effects, creates no data, executes nothing, and cannot delete or modify anything. The sanitization of credentials confirms it is read-only inspection of already-processed events.
From the tool's definition Tool explicitly 'Read[s] recent integration webhook and sync activity' with descriptions of viewing logs (action, status, event type, matched contact, error).
Attacks that exploit this kind of access
The rule that runs list_integration_activity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sequenzy Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_integration_activity, this is the rule to start with:
list_integration_activity is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sequenzy Mcp, apply this rule, and every list_integration_activity call is checked against it from then on.
Questions about list_integration_activity
Read recent integration webhook and sync activity, newest first. This is the log to check when an integration reports connected but contacts or events are not appearing: each row carries the action, status, event type, matched contact, and error. Payloads are sanitized at write time, so no credentials or secrets appear here. Activity is retained for 24 hours only. It is categorised as a Read tool in the Sequenzy Mcp MCP Server, which means it retrieves data without modifying state.
Register the Sequenzy MCP server in PolicyLayer and add a rule for list_integration_activity: 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 Sequenzy Mcp. Nothing to install.
list_integration_activity is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_integration_activity 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 list_integration_activity. 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.
list_integration_activity is provided by the Sequenzy MCP server (Sequenzy/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sequenzy, and thousands of servers like it.
This server
Across the catalogue