task_event_filter

task_event \u00b7 POST /taskEvent/filter \u2014 Returns events Required: q, from, size. Allowed values: analyticsEventAction=AttributeAdded|CustomAttributeAdded|OperatingSystemFamilyAdded|OperatingSystemFamilyPathsAdded|FunctionContainerArtifactPathAdded|UserActivatedAccount|UserAdded|Organizatio...

Server Vicarius vRx MCP Server space-c0wboy/vicarius-vrx-mcp-server
Category Read
Risk class Low
Parameters 00 required

What task_event_filter does on Vicarius vRx MCP Server

AI agents call task_event_filter to retrieve information from Vicarius vRx MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why task_event_filter needs a policy

Despite using POST (which can imply write operations), this tool's actual function is to retrieve and filter existing task event data with no side effects. The server description emphasizes 'read-only safety enforcement', and the tool parameters indicate query/retrieval rather than modification. This is a Read operation with low severity due to being informational only.

From the tool's definition Tool name contains 'filter', description states 'Returns events', and is a POST to /taskEvent/filter endpoint that queries existing task events with filter parameters (q, from, size).

Questions about task_event_filter

What does the task_event_filter tool do? +

task_event \u00b7 POST /taskEvent/filter \u2014 Returns events Required: q, from, size. Allowed values: analyticsEventAction=AttributeAdded|CustomAttributeAdded|OperatingSystemFamilyAdded|OperatingSystemFamilyPathsAdded|FunctionContainerArtifactPathAdded|UserActivatedAccount|UserAdded|OrganizationInstallationsAdded|UserActivity|IncidentEvent|NotificationIncidentEvent|InsightEvent|InternalServerAttributeScan|InternalServerAttributeScanEndpoints|ApplicationConfigEntryAdded|PublisherAdded|ApplicationAdded|EndpointAdded|ArchitectureAdded|FetchApplicationConfigWithCustomizedLocationFailed|FetchApplicationConfigWithCustomizedLocationSucceed|NotificationSourceAdded|OperatingSystemAdded|ProfilePictureAdded|VulnerabilityAdded|PatchAdded|ProfilePictureFailTooLarge|ProfilePictureFailOnUpload|UpdatedDevices|FetchDevices|NotificationsSentToDevice|NotificationsTrack|FetchNotificationById|ExternalReferenceSourceAdded|ExternalReferenceAdded|ExternalReferenceDisabled|UserAddedPassword|UserChangedPassword|UserForgotPassword|OrganizationAdded|UserAuthenticatedPassword|UserResetPassword|FunctionContainerArtifactAdded|FunctionContainerAdded|CapabilityAdded|OrganizationEndpointPublisherProductProcessesAdded|OrganizationExternalReferenceSourceAdded|PublisherProductCapabilityFunctionsAdded|StatusCheckAdded|CommandAdded|OrganizationEndpointFingerprintAdded|CPEStructureAdded|CPEStructureStatusAdded|CheckAdded|LinkAdded|TagAdded|InternalTagAdded|AttackVectorAdded|CheckCommandsAdded|HashtagAdded|OrganizationHashtagAdded|InternalServerAdded|TaskAdded|TaskEndpointsEventsAdded|OrganizationConfigEntryAdded|OrganizationEndpointConfigEntryAdded|OrganizationEndpointPatchPatchPackagesEntryAdded|OrganizationEndpointAutomationsEntryAdded|OrganizationEndpointLogsAdded|LicenseAgreementAdded|ProductRawEntryAdded|PrivacyPolicyAgreementAdded|UserPrivacyPolicyAgreementAdded|OrganizationEndpointGroup|RuleAdded|PathAdded|OrganizationEndpointPublisherProductProcessInternalTags|ScriptTemplateAdded|AutomationAdded|RoleAdded|ResourceAdded|PrivilegeAdded|RoleResourcePrivilegesAdded|OrganizationTeamAdded|PatchPackageXpatch|AuditLogs|BenchmarkResult|BenchmarkCheckResult|EndpointVulnerabilityEvidence|EndpointVulnerability|CPEInfoEvent|IntegrationAction. It is categorised as a Read tool in the Vicarius vRx MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on task_event_filter? +

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

What risk level is task_event_filter? +

task_event_filter is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit task_event_filter? +

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

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

task_event_filter is provided by the Vicarius vRx MCP Server MCP server (space-c0wboy/vicarius-vrx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.