ai_plan_metrics

Run a sample of planner goals against the on-device Foundation Model and report the aggregate score.

SERVERIconnect SOURCEiconnect-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-heznpc-iconnect/ai-plan-metrics.md

What ai_plan_metrics does on Iconnect

AI agents invoke ai_plan_metrics to trigger actions in Iconnect. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why ai_plan_metrics is rated High

The tool executes inference runs on an on-device Foundation Model, which constitutes triggering an external/local operation. It's not purely a read (it actively runs computation), not destructive or financial. The blast radius is medium since it consumes local compute resources and could expose planning data to model inference, but doesn't modify or delete persistent data.

From the tool's definition 'Run a sample of planner goals against the on-device Foundation Model and report the aggregate score' — actively runs/executes inference tasks against a model

Questions about ai_plan_metrics

What does the ai_plan_metrics tool do? +

Run a sample of planner goals against the on-device Foundation Model and report the aggregate score. It is categorised as a Execute tool in the Iconnect MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ai_plan_metrics? +

Register the Iconnect MCP server in PolicyLayer and add a rule for ai_plan_metrics: 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 Iconnect. Nothing to install.

What risk level is ai_plan_metrics? +

ai_plan_metrics is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit ai_plan_metrics? +

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

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

ai_plan_metrics is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Iconnect, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Iconnect's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.