AI agents call get_object_by_link to retrieve information from 1C MCP Toolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to fetch or retrieve an object identified by a link without modifying data. While the empty description reduces confidence, the function name strongly indicates a Read operation (get_*). If it retrieved and executed code or modified state, it would more likely be named execute_* or update_*. No evidence of side effects, destructive actions, or financial operations is present.
From the tool's definition Tool name 'get_object_by_link' suggests retrieval of an object via a link reference. The description is empty, but the naming pattern and context within sibling tools (get_metadata, get_access_rights, get_event_log) that are clearly Read operations suggests…
Documented attack patterns abuse exactly the kind of access get_object_by_link gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and 1C MCP Toolkit, and nothing reaches the server without passing your rules. This is the rule we recommend for get_object_by_link:
{
"version": "1",
"default": "deny",
"tools": {
"get_object_by_link": {}
}
}get_object_by_link is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_object_by_link. It is categorised as a Read tool in the 1C MCP Toolkit MCP Server, which means it retrieves data without modifying state.
Register the 1C MCP Toolkit MCP server in PolicyLayer and add a rule for get_object_by_link: 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 MCP Toolkit. Nothing to install.
get_object_by_link 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_by_link 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_by_link. 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_by_link is provided by the 1C MCP Toolkit MCP server (roctup/1c-mcp-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 1C MCP Toolkit tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 1C MCP Toolkit tools catalogued and risk-classified — across an index of 42,500+ MCP servers.