task_event_count_1

task_event \u00b7 POST /taskEvent/count \u2014 Count objects by stuff. Required: q. Allowed values: analyticsEventAction=AttributeAdded|CustomAttributeAdded|OperatingSystemFamilyAdded|OperatingSystemFamilyPathsAdded|FunctionContainerArtifactPathAdded|UserActivatedAccount|UserAdded|OrganizationIns...

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

What task_event_count_1 does on Vicarius vRx MCP Server

AI agents call task_event_count_1 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_count_1 needs a policy

This tool retrieves aggregated count data based on task event filters. It performs a read-only query operation with no side effects, data modification, or destructive capability. The use of POST with enumerated read-only filter values confirms it is a complex query endpoint, not a write, execute, or destructive operation.

From the tool's definition Tool name 'task_event_count_1' and description 'Count objects by stuff' indicate a counting/aggregation operation with no modification capability. The POST method is used for querying (common in APIs with complex filters), not for creating or modifying data.

Questions about task_event_count_1

What does the task_event_count_1 tool do? +

task_event \u00b7 POST /taskEvent/count \u2014 Count objects by stuff. Required: q. 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_count_1? +

Register the Vicarius vRx MCP Server MCP server in PolicyLayer and add a rule for task_event_count_1: 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_count_1? +

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

Can I rate-limit task_event_count_1? +

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

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

task_event_count_1 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.