AI agents call get_object_properties to retrieve information from Node Js Debugger MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves debugging information about object properties, consistent with read-only inspection operations. The empty description and similar naming patterns among debug inspection tools suggest this queries object metadata rather than executing code or modifying state.
From the tool's definition Tool name 'get_object_properties' combined with sibling tools focused on inspection (inspect_scopes, get_pause_info, get_script_source) and the server's stated capability of 'variable inspection' indicates this retrieves object property data during debugging…
Documented attack patterns abuse exactly the kind of access get_object_properties gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Node Js Debugger MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_object_properties:
{
"version": "1",
"default": "deny",
"tools": {
"get_object_properties": {}
}
}get_object_properties 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_properties. It is categorised as a Read tool in the Node Js Debugger MCP MCP Server, which means it retrieves data without modifying state.
Register the Node Js Debugger MCP server in PolicyLayer and add a rule for get_object_properties: 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 Node Js Debugger MCP. Nothing to install.
get_object_properties 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_properties 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_properties. 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_properties is provided by the Node Js Debugger MCP server (scriptedalchemy/devtools-debugger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 Node Js Debugger MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 Node Js Debugger MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.