get_object_metadata
A read tool on the 1c Forms MCP server.
This record as markdown: /tools/desko77-1c-formsserver/get-object-metadata.md
What get_object_metadata does on 1c Formsserver
AI agents call get_object_metadata to retrieve information from 1c Formsserver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_object_metadata is rated Low
Based on naming convention and context within a forms server that manages 1C:Enterprise forms, this tool appears to retrieve metadata about form objects without modifying state. The lack of description lowers confidence slightly, but the naming pattern and sibling tools (which include read operations like get_form_example, get_form_schema, get_form_info) suggest a read operation.
From the tool's definition Tool name 'get_object_metadata' indicates data retrieval. The 'get_' prefix is consistent with read-only query operations. Description is empty, limiting specificity.
Attacks that exploit this kind of access
The rule that runs get_object_metadata safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 1c Formsserver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_object_metadata, this is the rule to start with:
get_object_metadata is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 1c Formsserver, apply this rule, and every get_object_metadata call is checked against it from then on.
Questions about get_object_metadata
get_object_metadata is a read tool on the 1c Formsserver MCP server. It is categorised as a Read tool in the 1c Formsserver MCP Server, which means it retrieves data without modifying state.
Register the 1c Formsserver MCP server in PolicyLayer and add a rule for get_object_metadata: 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 1c Formsserver. Nothing to install.
get_object_metadata 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 get_object_metadata 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 get_object_metadata. 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.
get_object_metadata is provided by the 1c Formsserver MCP server (desko77/1c-formsserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 1c Formsserver, and thousands of servers like it.
This server
Across the catalogue