incident_event \u00b7 POST /incidentEvent/count \u2014 Count objects by stuff. Required: q. Allowed values: analyticsEventAction=AttributeAdded|CustomAttributeAdded|OperatingSystemFamilyAdded|OperatingSystemFamilyPathsAdded|FunctionContainerArtifactPathAdded|UserActivatedAccount|UserAdded|Organiz...
AI agents call incident_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.
Despite using the POST HTTP method, this tool's function is purely to query and count existing incident events based on filters. It retrieves aggregated data without side effects. The server description emphasizes 'read-only safety enforcement,' and this tool fits that pattern—counting/aggregating data is a Read operation.
From the tool's definition Tool performs a POST /incidentEvent/count operation to count objects; the description explicitly states it counts objects and accepts filter parameters (q, analyticsEventAction values).
Attacks that exploit this kind of access
incident_event \u00b7 POST /incidentEvent/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.
Register the Vicarius vRx MCP Server MCP server in PolicyLayer and add a rule for incident_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.
incident_event_count_1 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 incident_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.
Set action: deny in the PolicyLayer policy for incident_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.
incident_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.
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 →