organization_endpoint_patch_patch_packages_count

organization_endpoint_patch_patch_packages \u00b7 GET /organizationEndpointPatchPatchPackages/count \u2014 Count objects by stuff. Required: q, searchQuerys. Allowed values: analyticsEventAction=AttributeAdded|CustomAttributeAdded|OperatingSystemFamilyAdded|OperatingSystemFamilyPathsAdded|Functio...

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

What organization_endpoint_patch_patch_packages_count does on Vicarius vRx MCP Server

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

This is a read-only counting operation using HTTP GET. It queries and returns a count of patch packages matching specified criteria. The server description also explicitly states 'read-only safety enforcement'. No data is created, modified, deleted, or financial transactions are involved.

From the tool's definition GET /organizationEndpointPatchPatchPackages/count — Count objects by stuff. The tool uses HTTP GET and only counts/retrieves data with no side effects.

Questions about organization_endpoint_patch_patch_packages_count

What does the organization_endpoint_patch_patch_packages_count tool do? +

organization_endpoint_patch_patch_packages \u00b7 GET /organizationEndpointPatchPatchPackages/count \u2014 Count objects by stuff. Required: q, searchQuerys. 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 organization_endpoint_patch_patch_packages_count? +

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

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

Can I rate-limit organization_endpoint_patch_patch_packages_count? +

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

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

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