get_component_properties
AI agents call get_component_properties to retrieve information from Unity MCP with Ollama Integration without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description limiting full confidence, the name strongly suggests this tool queries and returns properties of existing components without modifying state. No write, execute, or destructive operations are implied.
From the tool's definition Tool name 'get_component_properties' indicates data retrieval of component properties from Unity GameObjects. The 'get_' prefix is a standard naming convention for read-only accessors.
Documented attack patterns abuse exactly the kind of access get_component_properties gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Unity MCP with Ollama Integration, and nothing reaches the server without passing your rules. This is the rule we recommend for get_component_properties:
{
"version": "1",
"default": "deny",
"tools": {
"get_component_properties": {}
}
} get_component_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_component_properties. It is categorised as a Read tool in the Unity MCP with Ollama Integration MCP Server, which means it retrieves data without modifying state.
Register the Unity MCP with Ollama Integration MCP server in PolicyLayer and add a rule for get_component_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 Unity MCP with Ollama Integration. Nothing to install.
get_component_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_component_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_component_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_component_properties is provided by the Unity MCP with Ollama Integration MCP server (zundamonnovrchatkaisetu/unity-mcp-ollama). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Unity MCP with Ollama Integration, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
37 Unity MCP with Ollama Integration tools catalogued and risk-classified — across an index of 43,000+ MCP servers.