mrjsnook -
Your question is tagged with a universalforwarder tag; so two solutions, depending on your deployment.
Small deployments, use sed (assuming you are using *nix) to read in the current value of maxKBps from limits.conf and update the value. Alternatively, use the large deployment solution.
Large deployments, create an app for specifically updating maxKBps in limits.conf and push the conf file out to the nodes which require the update.
Remember regardless of the path you choose, you must restart Splunk to enable configurations.
To verify values Splunk is reading from all limits.conf files use:
$SPLUNK_HOME/bin/splunk cmd btool limits list --debug
... View more