browse-objects

ServerWinCC Unified MCP Server
CategoryRead

WHAT IT DOES

What browse-objects does on WinCC Unified MCP Server

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

THE RISK

Low Risk

Why browse-objects needs a policy

This tool retrieves and enumerates existing objects from the SCADA system's configuration without modifying state, executing commands, or creating side effects. While browsing a SCADA system does expose system structure information (low sensitivity), the tool itself performs only passive queries.

From the tool's definition Tool description states it "Queries tags, elements, types, alarms, logging tags and basically anything that has a configured name, based on the provided filter criteria." The verb 'Queries' and the passive retrieval of configured objects with no mention of…

Documented attack patterns abuse exactly the kind of access browse-objects gives an agent:

POLICY

How to control browse-objects

PolicyLayer is an MCP gateway — it sits between your AI agents and WinCC Unified MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for browse-objects:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browse-objects": {}
  }
}

browse-objects is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register WinCC Unified MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More WinCC Unified MCP Server tools

Write acknowledge-alarms Acknowledge one or more alarms. Each alarm identifier must have the name of the configu Write reset-alarms Reset one or more alarms. Each alarm identifier must have the name of the configured al Write write-tag-values Updates tags, based on the provided TagValueInput list. If a TagValueInput does not def Read get-active-alarms Query active alarms from the provided systems. The filterString parameter must be a val Read get-logged-alarms Query logged alarms from the storage system. The filterString parameter must be a valid Read get-logged-tag-values Queries logged tag values from the database. Names is a mandatory parameter, each name Read get-tag-values Queries tag values from WinCC Unified. Based on the provided names list. If directRead is Other login-user Logs a user in to WinCC Unified using username and password. Stores the session token

All 9 WinCC Unified MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about browse-objects

What does the browse-objects tool do? +

Queries tags, elements, types, alarms, logging tags and basically anything that has a configured name, based on the provided filter criteria. Each filter parameter can be an array, and the logical relation between each item is an. It is categorised as a Read tool in the WinCC Unified MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browse-objects? +

Register the WinCC Unified MCP Server MCP server in PolicyLayer and add a rule for browse-objects: 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 WinCC Unified MCP Server. Nothing to install.

What risk level is browse-objects? +

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

Can I rate-limit browse-objects? +

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

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

browse-objects is provided by the WinCC Unified MCP Server MCP server (vogler75/winccua-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every WinCC Unified MCP Server tool call.

Start from WinCC Unified MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

9 WinCC Unified MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.